qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Alistair Francis <alistair23@gmail.com>
Cc: qemu-arm <qemu-arm@nongnu.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-2.11] target/arm: Report GICv3 sysregs present in ID registers if needed
Date: Wed, 15 Nov 2017 11:57:40 +0000	[thread overview]
Message-ID: <CAFEAcA-z_gfMr+=8c1kexo6iL--uxNVMzOnN0aox0FGAv3pHjQ@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKORH2jwGP4ULZv6B8=262OhznHkwOzONd9HFQoJkKzD=A@mail.gmail.com>

On 15 November 2017 at 01:14, Alistair Francis <alistair23@gmail.com> wrote:
> On Tue, Nov 7, 2017 at 7:01 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> The CPU ID registers ID_AA64PFR0_EL1, ID_PFR1_EL1 and ID_PFR1
>> have a field for reporting presence of GICv3 system registers.
>> We need to report this field correctly in order for Xen to
>> work as a guest inside QEMU emulation. We mustn't incorrectly
>> claim the sysregs exist when they don't, though, or Linux will
>> crash.
>>
>> Unfortunately the way we've designed the GICv3 emulation in QEMU
>> puts the system registers as part of the GICv3 device, which
>> may be created after the CPU proper has been realized. This
>> means that we don't know at the point when we define the ID
>> registers what the correct value is. Handle this by switching
>> them to calling a function at runtime to read the value, where
>> we can fill in the GIC field appropriately.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Is this going to make it into 2.11?

Yes, it's supposed to go into 2.11 -- I think I just forgot
to put it in the rc1 pullreq, but it'll go in rc2.

thanks
-- PMM

  reply	other threads:[~2017-11-15 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 15:01 [Qemu-devel] [PATCH for-2.11] target/arm: Report GICv3 sysregs present in ID registers if needed Peter Maydell
2017-11-07 18:04 ` Stefano Stabellini
2017-11-08  9:26 ` Richard Henderson
2017-11-15  1:14 ` Alistair Francis
2017-11-15 11:57   ` Peter Maydell [this message]
2017-11-16 17:03     ` Alistair Francis

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-z_gfMr+=8c1kexo6iL--uxNVMzOnN0aox0FGAv3pHjQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alistair23@gmail.com \
    --cc=patches@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sstabellini@kernel.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).