From: Peter Maydell <peter.maydell@linaro.org>
To: Christoffer Dall <cdall@linaro.org>
Cc: James Morse <james.morse@arm.com>,
kvm-devel <kvm@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
gengdongjiu <gengdongjiu@huawei.com>,
wangxiongfeng2@huawei.com, wuquanming@huawei.com,
huangshaoyu@huawei.com,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
Andre Przywara <andre.przywara@arm.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [PATCH] kvm: pass the virtual SEI syndrome to guest OS
Date: Tue, 21 Mar 2017 22:10:41 +0000 [thread overview]
Message-ID: <CAFEAcA_NBvRQpuXJ2iZs_8n3b6920Z6E5ueuiAeF-4JCcqPRxQ@mail.gmail.com> (raw)
In-Reply-To: <20170321193933.GB31111@cbox>
On 21 March 2017 at 19:39, Christoffer Dall <cdall@linaro.org> wrote:
> My confusion here comes from not thinking about QEMU or KVM as firmware,
> but as the machine, so it would be sort of like the functionality is
> baked into hardware rather than firmware.
There is precedent for that kind of thing -- we implement PSCI
in KVM/QEMU for the guest, though in real hardware it would be
provided by firmware at EL3.
thanks
-- PMM
next prev parent reply other threads:[~2017-03-21 22:17 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 7:55 [PATCH] kvm: pass the virtual SEI syndrome to guest OS Dongjiu Geng
2017-03-20 11:24 ` Marc Zyngier
2017-03-20 12:28 ` gengdongjiu
2017-03-20 13:58 ` Marc Zyngier
2017-03-20 15:08 ` James Morse
2017-03-21 6:32 ` gengdongjiu
2017-03-21 11:34 ` Christoffer Dall
2017-03-21 19:11 ` James Morse
2017-03-21 19:39 ` Christoffer Dall
2017-03-21 22:10 ` Peter Maydell [this message]
2017-03-22 11:15 ` Marc Zyngier
2017-03-28 10:48 ` James Morse
2017-03-28 11:23 ` Christoffer Dall
2017-03-28 11:33 ` Peter Maydell
2017-03-28 13:27 ` James Morse
2017-03-28 11:54 ` Achin Gupta
2017-03-28 12:16 ` gengdongjiu
2017-03-28 13:40 ` James Morse
2017-03-29 9:36 ` gengdongjiu
2017-03-29 10:36 ` Achin Gupta
2017-03-29 11:58 ` Laszlo Ersek
2017-03-29 12:51 ` Michael S. Tsirkin
2017-03-29 13:36 ` Laszlo Ersek
2017-03-29 13:54 ` Michael S. Tsirkin
2017-03-29 13:56 ` Punit Agrawal
2017-04-06 12:35 ` gengdongjiu
2017-04-06 18:55 ` Laszlo Ersek
2017-04-07 2:52 ` gengdongjiu
2017-04-07 9:21 ` Laszlo Ersek
2017-04-21 13:27 ` gengdongjiu
2017-04-24 11:27 ` Laszlo Ersek
2017-03-29 14:36 ` gengdongjiu
2017-03-29 14:48 ` Christoffer Dall
2017-03-29 15:37 ` Laszlo Ersek
2017-03-29 17:44 ` Christoffer Dall
2017-03-30 1:22 ` gengdongjiu
2017-03-28 12:22 ` Christoffer Dall
2017-03-28 13:24 ` Achin Gupta
2017-03-28 13:40 ` Christoffer Dall
2017-03-21 13:10 ` James Morse
2017-03-22 13:37 ` gengdongjiu
2017-03-22 18:56 ` James Morse
2017-03-21 6:07 ` gengdongjiu
2017-03-21 13:51 ` kbuild test robot
2017-03-22 3:20 ` gengdongjiu
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_NBvRQpuXJ2iZs_8n3b6920Z6E5ueuiAeF-4JCcqPRxQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=andre.przywara@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cdall@linaro.org \
--cc=gengdongjiu@huawei.com \
--cc=huangshaoyu@huawei.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=wangxiongfeng2@huawei.com \
--cc=will.deacon@arm.com \
--cc=wuquanming@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).