Subject: Re: [PATCH RFC] arm64: introduce mm_context_t flags
To: Yury Norov <ynorov@caviumnetworks.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
References: <20170731144825.31322-1-ynorov@caviumnetworks.com>
From: Pratyush Anand <panand@redhat.com>
Message-ID: <5e0f1ae7-3a69-0d1c-3f33-ddb44ed8b6c5@redhat.com>
Date: Tue, 1 Aug 2017 09:10:05 +0530
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170731144825.31322-1-ynorov@caviumnetworks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 583
Lines: 19


On Monday 31 July 2017 08:18 PM, Yury Norov wrote:
>   - If we start using TIF flags here, we cannot easily add new mm_context
>     specific bits because they may mess with TIF ones.

This one seems convincing argument. ATM do you have any mm_context flag which 
would you like to incorporate?

> 
> I think that this is not what was intended when you added new field in
> mm_context_t.
> 
> In this patch the MMCF_AARCH32 flag is introduced, where MMCF prefix stands for
> mm_context_t flags. And the new flag is used for uprobes code instead of TIF_32BIT.

-- 
Regards
Pratyush