linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter.maydell@linaro.org (Peter Maydell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] arm64: kernel: Add support for User Access Override
Date: Fri, 19 Feb 2016 16:54:17 +0000	[thread overview]
Message-ID: <CAFEAcA_uAG1hX2a3n8FSJpB704wzJeXzijHSETJ2B6OR0g=nJw@mail.gmail.com> (raw)
In-Reply-To: <20160219164606.GD12864@e104818-lin.cambridge.arm.com>

On 19 February 2016 at 16:46, Catalin Marinas <catalin.marinas@arm.com> wrote:
> On Fri, Feb 19, 2016 at 03:38:44PM +0000, Peter Maydell wrote:
>> This is more of a heads-up than a demand that you Do Something,
>> but perhaps somebody has a clever idea...
>
> Only if Qemu had its own MIDR/REVIDR ;) (and patch the instruction like
> other errata workarounds).

Smiley noted, but FWIW the relevant CPUs advertise themselves as
MIDR 0x411fd070 REVIDR 0 (A57) and MIDR 0x410fd034 REVIDR 0 (A53),
and it should be harmless to patch the ID_AA64MMFR2 read to always
return 0 on any A53 or A57 including h/w, because they'll read as
zero anyway...

So it comes down to how much we want to work around QEMU "errata".

thanks
-- PMM

  reply	other threads:[~2016-02-19 16:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 14:58 [PATCH v2 0/5] arm64: kernel: Add support for User Access Override James Morse
2016-02-05 14:58 ` [PATCH v2 1/5] arm64: cpufeature: Change read_cpuid() to use sysreg's mrs_s macro James Morse
2016-02-05 14:58 ` [PATCH v2 2/5] arm64: add ARMv8.2 id_aa64mmfr2 boiler plate James Morse
2016-03-03 17:59   ` Christopher Covington
2016-03-03 18:27     ` Robin Murphy
2016-03-03 19:03       ` Christopher Covington
2016-03-03 19:19         ` Will Deacon
2016-03-04 10:20           ` Suzuki K. Poulose
2016-03-04 13:37             ` James Morse
2016-03-04 13:54               ` Robin Murphy
2016-03-04 14:59         ` Mark Rutland
2016-03-04 18:15           ` Christopher Covington
2016-02-05 14:58 ` [PATCH v2 3/5] arm64: kernel: Add support for User Access Override James Morse
2016-02-18 12:26   ` Catalin Marinas
2016-02-05 14:58 ` [PATCH v2 4/5] arm64: cpufeature: Test 'matches' pointer to find the end of the list James Morse
2016-02-05 14:58 ` [PATCH v2 5/5] arm64: kernel: Don't toggle PAN on systems with UAO James Morse
2016-02-18 14:36   ` Catalin Marinas
2016-02-18 14:43     ` James Morse
2016-02-05 15:40 ` [PATCH v2 0/5] arm64: kernel: Add support for User Access Override Arnd Bergmann
2016-02-09  9:47   ` Will Deacon
2016-02-18 18:03 ` Catalin Marinas
2016-02-19 15:38   ` Peter Maydell
2016-02-19 16:46     ` Catalin Marinas
2016-02-19 16:54       ` Peter Maydell [this message]
2016-02-19 16:57         ` Ard Biesheuvel
2016-02-19 17:03           ` Peter Maydell
2016-03-07 16:43 ` James Morse
2016-03-07 17:23   ` Russell King - ARM Linux
2016-03-07 17:40     ` James Morse
2016-03-07 17:51       ` Russell King - ARM Linux
2016-03-07 17:38   ` Catalin Marinas
2016-03-07 20:54     ` Kees Cook
2016-03-08 17:19       ` Catalin Marinas
2016-03-08 17:39         ` Kees Cook
2016-03-08 18:22           ` Catalin Marinas
2016-03-08 18:27             ` Kees Cook

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='CAFEAcA_uAG1hX2a3n8FSJpB704wzJeXzijHSETJ2B6OR0g=nJw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --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).