qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Christoffer Dall <christoffer.dall@arm.com>
Subject: Re: [Qemu-devel] [PATCH 4/5] target/arm: Fill in ARMISARegisters for kvm32
Date: Mon, 29 Oct 2018 15:56:58 +0000	[thread overview]
Message-ID: <1ca884ee-8bf5-77fa-dfd8-b275da1ec846@arm.com> (raw)
In-Reply-To: <CAFEAcA_x_g3TEnC=A=EjugWRo33C1BwL2YL=iJQXgzre7gJQLA@mail.gmail.com>

On 29/10/18 15:48, Peter Maydell wrote:
> On 29 October 2018 at 15:40, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> My temptation would be not to expose it at all when running on a v7
>> core, and return an error rather than zero.
>>
>> The other issue is that we currently don't support running 32bit KVM on
>> any ARMv8 platform, as we strictly check the CPUs we want to run on (A7
>> and A15). I remember seeing patches that would allow any host core to be
>> used (similar to what we have on the 64bit side), but that never made it
>> in the tree.
> 
> Ah, that's convenient in some ways. It means we can define the
> API to be "for v7, no register available via the ONE_REG API;
> for v8, always present", provided we add the constant and the
> support before we turn on any actual v8 CPUs for 32-bit KVM
> (avoiding the awkward case of "v8 but kernel doesn't expose
> MVFR2").
> 
> I don't think we particularly care about the 32-bit-kvm-on-v8
> part, but it would be good to nail down this wrinkle so we don't
> forget about it, maybe ?

Absolutely. I'll write something up.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2018-10-29 15:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 11:37 [Qemu-devel] [PATCH 0/5] target/arm: KVM vs ARMISARegisters Richard Henderson
2018-10-24 11:37 ` [Qemu-devel] [PATCH 1/5] target/arm: Install ARMISARegisters from kvm host Richard Henderson
2018-11-02 14:24   ` Peter Maydell
2018-10-24 11:37 ` [Qemu-devel] [PATCH 2/5] target/arm: Fill in ARMISARegisters for kvm64 Richard Henderson
2018-10-29 14:58   ` Peter Maydell
2018-10-29 16:03     ` Richard Henderson
2018-11-02 14:37       ` Peter Maydell
2018-10-24 11:37 ` [Qemu-devel] [PATCH 3/5] target/arm: Introduce read_sys_reg32 for kvm32 Richard Henderson
2018-10-24 12:49   ` Richard Henderson
2018-11-02 14:30   ` Peter Maydell
2018-11-02 14:37     ` Richard Henderson
2018-10-24 11:37 ` [Qemu-devel] [PATCH 4/5] target/arm: Fill in ARMISARegisters " Richard Henderson
2018-10-29 15:13   ` Peter Maydell
2018-10-29 15:21     ` Peter Maydell
2018-10-29 15:40       ` Marc Zyngier
2018-10-29 15:48         ` Peter Maydell
2018-10-29 15:56           ` Marc Zyngier [this message]
2018-10-24 11:37 ` [Qemu-devel] [PATCH 5/5] target/arm: Convert t32ee from feature bit to isar3 test Richard Henderson
2018-11-02 14:34   ` Peter Maydell
2018-11-01 17:26 ` [Qemu-devel] [PATCH 0/5] target/arm: KVM vs ARMISARegisters Alex Bennée
2018-11-01 17:30   ` Peter Maydell
2018-11-01 18:09     ` Peter Maydell

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=1ca884ee-8bf5-77fa-dfd8-b275da1ec846@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).