From: James Morse <james.morse@arm.com>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: marc.zyngier@arm.com, christoffer.dall@linaro.org,
rkrcmar@redhat.com, linux@armlinux.org.uk,
tbaicar@codeaurora.org, imammedo@redhat.com,
zhaoshenglong@huawei.com, peter.maydell@linaro.org,
pbonzini@redhat.com, qemu-devel@nongnu.org, qemu-arm@nongnu.org,
lersek@redhat.com, ard.biesheuvel@linaro.org,
mtsirkin@redhat.com, drjones@redhat.com, ben@skyportsystems.com,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, xiexiuqi@huawei.com,
wangxiongfeng2@huawei.com, songwenjun@huawei.com,
wuquanming@huawei.com, huangshaoyu@huawei.com
Subject: Re: [Qemu-devel] [PATCH v3 1/3] arm64: kvm: support kvmtool to detect RAS extension feature
Date: Thu, 04 May 2017 16:49:07 +0100 [thread overview]
Message-ID: <590B4D73.60000@arm.com> (raw)
In-Reply-To: <5908A5BC.1060202@arm.com>
Hi Dongjiu Geng,
On 02/05/17 16:29, James Morse wrote:
> I think we need a new API for injecting SError for SEI from Qemu/kvmtool, but it
> shouldn't be related to the RAS extensions. All v8.0 CPUs have HCR_EL2.VSE, so
> we need to know KVM supports this API.
Thinking about this some more, it is slightly more nuanced, KVM can always
provide an API to inject SError, but it can only set the VSESR if the CPU has
the RAS Extensions.
Only offering the inject-SError API call if we can also set the VSESR looks a
bit funny, but no-one has needed the no-ESR version so far.
I still don't think we should let user-space make the 'RAS Extensions means
VSESR' logical step.
So my comments on this patch become:
Don't read id registers directly, use cpus_have_cap() which handles features
that differ across CPUs or were turned off at compile time.
Please don't call this 'KVM_CAP_ARM_RAS_EXTENSION', if we are building an API to
inject SError, call it that instead.
Thanks,
James
next prev parent reply other threads:[~2017-05-04 15:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 5:37 [Qemu-devel] [PATCH v3 1/3] arm64: kvm: support kvmtool to detect RAS extension feature Dongjiu Geng
2017-04-30 5:37 ` [Qemu-devel] [PATCH v3 2/3] arm64: kvm: inject SError with virtual syndrome Dongjiu Geng
2017-05-02 8:03 ` Christoffer Dall
2017-05-02 12:20 ` gengdongjiu
2017-05-02 15:37 ` James Morse
2017-05-05 13:19 ` gengdongjiu
2017-05-12 17:24 ` James Morse
2017-05-21 9:08 ` gengdongjiu
2017-04-30 5:37 ` [Qemu-devel] [PATCH v3 3/3] arm/arm64: signal SIBGUS and inject SEA Error Dongjiu Geng
2017-05-02 15:41 ` James Morse
2017-05-02 7:56 ` [Qemu-devel] [PATCH v3 1/3] arm64: kvm: support kvmtool to detect RAS extension feature Christoffer Dall
2017-05-02 11:05 ` gengdongjiu
2017-05-02 12:15 ` gengdongjiu
2017-05-02 15:48 ` Paolo Bonzini
2017-05-04 8:19 ` James Morse
2017-05-02 15:29 ` James Morse
2017-05-04 15:49 ` James Morse [this message]
2017-05-05 12:44 ` gengdongjiu
2017-06-26 5:22 ` 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=590B4D73.60000@arm.com \
--to=james.morse@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ben@skyportsystems.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=gengdongjiu@huawei.com \
--cc=huangshaoyu@huawei.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lersek@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mtsirkin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=songwenjun@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=wangxiongfeng2@huawei.com \
--cc=wuquanming@huawei.com \
--cc=xiexiuqi@huawei.com \
--cc=zhaoshenglong@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).