From: Marc Zyngier <marc.zyngier@arm.com>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: <christoffer.dall@linaro.org>, <pbonzini@redhat.com>,
<rkrcmar@redhat.com>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <james.morse@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] KVM: arm64: pass vcpu esr_el2 and far_el2 sysre to user space
Date: Mon, 07 Aug 2017 20:07:12 +0100 [thread overview]
Message-ID: <86r2wnxkm7.fsf@arm.com> (raw)
In-Reply-To: <1502133454-5905-1-git-send-email-gengdongjiu@huawei.com> (Dongjiu Geng's message of "Tue, 8 Aug 2017 03:17:34 +0800")
On Tue, Aug 08 2017 at 3:17:34 am BST, Dongjiu Geng <gengdongjiu@huawei.com> wrote:
> For the firmware-first RAS solution, SEA and SEI is injected
> by the user space, user space needs to know the vcpu's esr_el2 and
> far_el2 value, so add them to sysreg. user space uses
> the IOCTL KVM_GET_ONE_REG can get their value.
Are we playing a game here? Look at my earlier reply: No _EL2 register
will ever be exposed as such to userspace in the context of an EL1 VM.
So if you want that information, extract it, expose what is required,
strictly what is required, and only when it is required.
In the meantime, I'm NAKing this patch, and any patch that will expose
_EL2 registers outside of nested virtualization.
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2017-08-07 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 19:17 [PATCH v2] KVM: arm64: pass vcpu esr_el2 and far_el2 sysre to user space Dongjiu Geng
2017-08-07 19:07 ` Marc Zyngier [this message]
2017-08-07 23:53 ` 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=86r2wnxkm7.fsf@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=gengdongjiu@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=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=will.deacon@arm.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