linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: james.morse@arm.com (James Morse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 6/6] arm64: kernel: Add support for Privileged Access Never
Date: Thu, 23 Jul 2015 08:58:26 +0100	[thread overview]
Message-ID: <55B09EA2.8070101@arm.com> (raw)
In-Reply-To: <20150722181440.GS6650@arm.com>

On 22/07/15 19:14, Will Deacon wrote:
> On Wed, Jul 22, 2015 at 07:04:54PM +0100, James Morse wrote:
>> On 22/07/15 18:01, Will Deacon wrote:
>>> I've applied your series with the exception of this last one, as it
>>> conflicts with some other patches I have queued for 4.3. Please can you
>>> rebase this against the arm64 "devel" branch? (usually it would be
>>> for-next/core, but I'm holding off stabilising until -rc4 since allmodconfig
>>> build is broken atm).
>>
>> The version of patch 5 "arm64: kernel: Add optional CONFIG_ parameter to
>> ALTERNATIVE()" in your tree has:
>>
>>> [will: removed unused asm macro changes for now to avoid conflicts]
>>
>> Those were used in arch/arm64/lib/clear_user.S and friends.
>> I shall remove the 'CONFIG_ARM64_PAN' from those four asm files - it can be
>> tidied up later.
> 
> Ah, damn, I didn't realise you'd made the ALTERNATIVE macro work for both
> C and asm. The reason I changed it is because I don't know what's best to
> do with the new alternative_if_not macros -- having an enabled argument
> for the _else and _endif variants is really odd.
> 
> I think the options are:
> 
>   (1) Just spit out a NOP (you're current approach)
>   (2) Use #ifdefs at the caller
>   (3) Only have the option for alternative_insn
>   (4) Add the option to all the alternative_ macros
> 
> What do you reckon?

I would go with (1) for now, it only affects four functions, not the
uaccess.h macros, where it would be inlined all over the place.

(4) can be a future optimisation.


James

  reply	other threads:[~2015-07-23  7:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 12:23 [PATCH v3 0/6] arm64: kernel: Add support for Privileged Access Never James Morse
2015-07-21 12:23 ` [PATCH v3 1/6] arm64: kernel: Add cpuid_feature_extract_field() for 4bit sign extension James Morse
2015-07-21 12:32   ` Catalin Marinas
2015-07-21 12:23 ` [PATCH v3 2/6] arm64: kernel: preparatory: Move config_sctlr_el1 James Morse
2015-07-21 12:23 ` [PATCH v3 3/6] arm64: kernel: Add cpufeature 'enable' callback James Morse
2015-07-21 12:23 ` [PATCH v3 4/6] arm64: kernel: Add min_field_value and use '>=' for feature detection James Morse
2015-07-21 12:33   ` Catalin Marinas
2015-07-21 12:23 ` [PATCH v3 5/6] arm64: kernel: Add optional CONFIG_ parameter to ALTERNATIVE() James Morse
2015-07-21 12:23 ` [PATCH v3 6/6] arm64: kernel: Add support for Privileged Access Never James Morse
2015-07-21 12:38   ` Catalin Marinas
2015-07-22 17:01     ` Will Deacon
2015-07-22 18:04       ` James Morse
2015-07-22 18:14         ` Will Deacon
2015-07-23  7:58           ` James Morse [this message]
2015-07-22 18:05       ` [PATCH v4] " James Morse
2015-07-23 13:07         ` Will Deacon
2015-07-24 15:14           ` James Morse
2015-07-24 16:56             ` Will Deacon
2015-07-23 12:00     ` [PATCH v3 6/6] " Will Deacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B09EA2.8070101@arm.com \
    --to=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).