From: Guoheyi <guoheyi@huawei.com>
To: <qemu-arm@nongnu.org>, <qemu-devel@nongnu.org>,
<linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Peter Maydell <peter.maydell@linaro.org>,
James.Morse@arm.com,
wanghaibin 00208455 <wanghaibin.wang@huawei.com>
Subject: [RFC] Add virtual SDEI support in qemu
Date: Sat, 13 Jul 2019 17:53:57 +0800 [thread overview]
Message-ID: <1b0aa6b2-80b1-a72e-6849-7323c3b9c6bc@huawei.com> (raw)
Hi folks,
Do it make sense to implement virtual SDEI in qemu? So that we can have
the standard way for guest to handle NMI watchdog, RAS events and
something else which involves SDEI in a physical ARM64 machine.
My basic idea is like below:
1. Change a few lines of code in kvm to allow unhandled SMC invocations
(like SDEI) to be sent to qemu, with exit reason of KVM_EXIT_HYPERCALL,
so we don't need to add new API.
2. qemu handles supported SDEI calls just as the spec says for what a
hypervisor should do for a guest OS.
3. For interrupts bound to hypervisor, qemu should stop injecting the
IRQ to guest through KVM, but jump to the registered event handler
directly, including context saving and restoring. Some interrupts like
virtual timer are handled by kvm directly, so we may refuse to bind such
interrupts to SDEI events.
Any comment or suggestion will be really appreciated.
Heyi
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-07-13 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 9:53 Guoheyi [this message]
2019-07-15 13:41 ` [RFC] Add virtual SDEI support in qemu 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
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=1b0aa6b2-80b1-a72e-6849-7323c3b9c6bc@huawei.com \
--to=guoheyi@huawei.com \
--cc=James.Morse@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.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).