From: Gavin Shan <gshan@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jones <drjones@redhat.com>,
jthierry@redhat.com, Alexey Kardashevskiy <aik@ozlabs.ru>,
Marc Zyngier <maz@kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Eric Auger <eric.auger@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>, Shan Gavin <shan.gavin@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RESEND RFC PATCH v2 1/2] target/arm: Allow to inject SError interrupt
Date: Thu, 13 Feb 2020 22:09:44 +1100 [thread overview]
Message-ID: <e7f614cc-ebd2-877d-2720-02d7d6edf152@redhat.com> (raw)
In-Reply-To: <a0ff5b47-876d-533f-ea18-e53ee371ceba@linaro.org>
On 2/13/20 4:39 PM, Richard Henderson wrote:
> On 2/12/20 7:49 PM, Gavin Shan wrote:
>> On 2/12/20 10:34 PM, Peter Maydell wrote:
>>> Yeah, this is on my list to look at; Richard Henderson also could
>>> have a look at it. From a quick scan I suspect you may be missing
>>> handling for AArch32.
>>>
>>
>> [Thanks for copying Richard Henderson]
>>
>> Yes, the functionality is only supported on aarch64 currently by intention
>> because the next patch enables it on "max" and "host" CPU models and both
>> of them are running in aarch64 mode.
>
> We shouldn't leave the aarch32 exception entry paths unimplemented though. C.f.
>
> AArch32.TakePhysicalSErrorException()
> AArch32.TakeVirtualSErrorException()
>
> It really shouldn't be more than a couple of lines, just like
> arm_cpu_do_interrupt_aarch64. Remember both arm_cpu_do_interrupt_aarch32 and
> arm_cpu_do_interrupt_aarch32_hyp.
>
Thanks for the details. The SError injection for aarch32 will be included in v3.
>> However, it seems there is a long list of aarch32 CPU models, defined
>> in target/arm/cpu.c::arm_cpus. so which CPU models you prefer to see with
>> this supported? I think we might choose one or two popular CPU models if
>> you agree.
>
> Even qemu-system-aarch64 -cpu max can exercise this path when EL1 is running in
> aarch32 mode. Admittedly it would be easier if we had the rest of the plumbing
> so that -cpu max,aarch64=off worked.
>
> FWIW, the rest of the patch looks good.
>
I think "-cpu max,aarch64=off" is only valid when KVM is enabled? If that's true,
the ioctl(cpu, KVM_SET_VCPU_EVENTS, &events) already worked for aarch32 or aarch64
guest if I'm correct enough. But yes, I need to test it because I never tested this
series on aarch32 guest :)
Thanks,
Gavin
next prev parent reply other threads:[~2020-02-13 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:05 [RESEND RFC PATCH v2 1/2] target/arm: Allow to inject SError interrupt Gavin Shan
2020-02-12 6:39 ` Gavin Shan
2020-02-12 11:34 ` Peter Maydell
2020-02-13 3:49 ` Gavin Shan
2020-02-13 5:39 ` Richard Henderson
2020-02-13 11:09 ` Gavin Shan [this message]
2020-02-13 10:31 ` Peter Maydell
2020-02-14 2:25 ` Gavin Shan
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=e7f614cc-ebd2-877d-2720-02d7d6edf152@redhat.com \
--to=gshan@redhat.com \
--cc=aik@ozlabs.ru \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jthierry@redhat.com \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@gmail.com \
/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).