From: gengdongjiu <gengdongjiu@huawei.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
<christoffer.dall@linaro.org>, <pbonzini@redhat.com>,
<rkrcmar@redhat.com>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <linux-arm-kernel@lists.infradead.org>,
<kvmarm@lists.cs.columbia.edu>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, James Morse <James.Morse@arm.com>
Subject: Re: [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg
Date: Tue, 8 Aug 2017 00:23:31 +0800 [thread overview]
Message-ID: <b834276b-b47d-51fb-7661-3eb5a2f6a68d@huawei.com> (raw)
In-Reply-To: <9fe6aa3a-98f9-6cae-6932-054858b54744@arm.com>
Hi Marc,
As James's suggestion, I move injection SEA Error logic to the user space(Qemu), Qemu sets the related guest OS esr/elr/pstate/spsr
through IOCTL KVM_SET_ONE_REG. For the SEA, when Qemu sets the esr_el1.IL bit, it needs to refer to esr_el2.IL, else Qemu does not know the trapped
instruction was a 16-bit or a 32-bit instruction, also it needs to set far_el1 using far_el2, because this is synchronization abort.
On 2017/8/7 23:57, Marc Zyngier wrote:
> +James, since he deals with all things RAS. Please keep him on CC at all
> times.
>
> On 07/08/17 17:08, Dongjiu Geng wrote:
>> For the firmware-first RAS solution, SEA and SEI is injected
>> by the user space, user space needs to know the esr_el2 and
>> far_el2's value, so add them to sysreg. user space uses
>> the IOCTL KVM_GET_ONE_REG can get their value.
>
> No.
>
> This has zero purpose being exposed to userspace. Userspace sees a VM
> that runs at EL1, and nothing else, so exposing EL2 registers doesn't
> make *any* sense.
>
> If you want something to be exposed to userspace, it has to be properly
> abstracted and describe something that is relevant to the VM. An EL2
> register satisfies none of these conditions.
>
>>
>> Signed-off-by: Dongjiu Geng <gengdongjiu@huawei.com>
>> Signed-off-by: Quanming Wu <wuquanming@huawei.com>
>> ---
>> arch/arm64/include/asm/kvm_host.h | 6 ++++--
>> arch/arm64/kvm/sys_regs.c | 6 ++++++
>> 2 files changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
>> index b6242fb..6063eec 100644
>> --- a/arch/arm64/include/asm/kvm_host.h
>> +++ b/arch/arm64/include/asm/kvm_host.h
>> @@ -103,10 +103,12 @@ enum vcpu_sysreg {
>> TTBR0_EL1, /* Translation Table Base Register 0 */
>> TTBR1_EL1, /* Translation Table Base Register 1 */
>> TCR_EL1, /* Translation Control Register */
>> - ESR_EL1, /* Exception Syndrome Register */
>> + ESR_EL1, /* Exception Syndrome Register for EL1 */
>> + ESR_EL2, /* Exception Syndrome Register for EL2 */
>> AFSR0_EL1, /* Auxiliary Fault Status Register 0 */
>> AFSR1_EL1, /* Auxiliary Fault Status Register 1 */
>> - FAR_EL1, /* Fault Address Register */
>> + FAR_EL1, /* Fault Address Register for EL1 */
>> + FAR_EL2, /* Fault Address Register for EL2 */
>> MAIR_EL1, /* Memory Attribute Indirection Register */
>> VBAR_EL1, /* Vector Base Address Register */
>> CONTEXTIDR_EL1, /* Context ID Register */
>> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
>> index 0e26f8c..0c286bf 100644
>> --- a/arch/arm64/kvm/sys_regs.c
>> +++ b/arch/arm64/kvm/sys_regs.c
>> @@ -987,9 +987,15 @@ static const struct sys_reg_desc sys_reg_descs[] = {
>> /* ESR_EL1 */
>> { Op0(0b11), Op1(0b000), CRn(0b0101), CRm(0b0010), Op2(0b000),
>> access_vm_reg, reset_unknown, ESR_EL1 },
>> + /* ESR_EL2 */
>> + { Op0(0b11), Op1(0b100), CRn(0b0101), CRm(0b0010), Op2(0b000),
>> + access_vm_reg, reset_unknown, ESR_EL2 },
>> /* FAR_EL1 */
>> { Op0(0b11), Op1(0b000), CRn(0b0110), CRm(0b0000), Op2(0b000),
>> access_vm_reg, reset_unknown, FAR_EL1 },
>> + /* FAR_EL2 */
>> + { Op0(0b11), Op1(0b100), CRn(0b0110), CRm(0b0000), Op2(0b000),
>> + access_vm_reg, reset_unknown, FAR_EL2 },
>> /* PAR_EL1 */
>> { Op0(0b11), Op1(0b000), CRn(0b0111), CRm(0b0100), Op2(0b000),
>> NULL, reset_unknown, PAR_EL1 },
>>
>
> Also, what do you return here? All you're doing to return to userspace
> is 0x1de7ec7edbadc0deULL (which perfectly matches this patch).
>
> So for all intents and purposes, this patch is pretty useless.
>
> Thanks,
>
> M.
>
next prev parent reply other threads:[~2017-08-07 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 16:08 Dongjiu Geng
2017-08-07 15:57 ` Marc Zyngier
2017-08-07 16:23 ` gengdongjiu [this message]
2017-08-07 16:56 ` Marc Zyngier
2017-08-07 18:59 ` gengdongjiu
2017-08-07 16:59 ` James Morse
2017-08-07 17:43 ` gengdongjiu
2017-08-08 16:27 ` James Morse
2017-08-08 18:27 ` 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=b834276b-b47d-51fb-7661-3eb5a2f6a68d@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=James.Morse@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--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=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
all inboxes | Powered by JetHome®