From: Dave Martin <Dave.Martin@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
Guoheyi <guoheyi@huawei.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Qemu-devel] [RFC] Add virtual SDEI support in qemu
Date: Tue, 16 Jul 2019 09:30:50 +0100 [thread overview]
Message-ID: <20190716083050.GK2790@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20190715134848.GI56232@lakrids.cambridge.arm.com>
On Mon, Jul 15, 2019 at 02:48:49PM +0100, Mark Rutland wrote:
> On Mon, Jul 15, 2019 at 02:41:00PM +0100, Dave Martin wrote:
[...]
> > So long as KVM_EXIT_HYPERCALL reports sufficient information so that
> > userspace can identify the cause as an SMC and retrieve the SMC
> > immediate field, this seems feasible.
> >
> > For its own SMCCC APIs, KVM exclusively uses HVC, so rerouting SMC to
> > userspace shouldn't conflict.
>
> Be _very_ careful here! In systems without EL3 (and without NV), SMC
> UNDEFs rather than trapping to EL2. Given that, we shouldn't build a
> hypervisor ABI that depends on SMC.
Good point. I was hoping that was all ancient history by now, but if
not...
[...]
Cheers
---Dave
next prev parent reply other threads:[~2019-07-16 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 9:53 [Qemu-devel] [RFC] Add virtual SDEI support in qemu Guoheyi
2019-07-15 13:41 ` Dave Martin
2019-07-15 13:48 ` Mark Rutland
2019-07-15 14:26 ` James Morse
2019-07-15 14:44 ` Mark Rutland
2019-07-16 8:47 ` Dave Martin
2019-07-19 1:49 ` Guoheyi
2019-07-16 8:30 ` Dave Martin [this message]
2019-07-16 8:46 ` Marc Zyngier
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=20190716083050.GK2790@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--cc=guoheyi@huawei.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).