Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from userspace

From	gengdongjiu <gengdj.1984@gmail.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from userspace
Date	2017-09-27 17:40 +0200
Message-ID	<uumBj-4YL-1@gated-at.bofh.it> (permalink)
References	(3 earlier) <upar8-4lj-17@gated-at.bofh.it> <upC42-5rQ-15@gated-at.bofh.it> <us4yR-6pb-7@gated-at.bofh.it> <uszt0-8us-15@gated-at.bofh.it> <uuixH-1FJ-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

>> What you may be seeing is some awkwardness with the change in the SError ESR
>> with v8.2. Previously the VSE mechanism injected an impdef SError, (but they
>> were all impdef so it didn't matter).
>> With VSESR_EL2 KVM has to specify one, and all-zeros is a bad choice as this
>> means 'classified as a RAS error ... unknown!'.
>>
>> I have a patch in the upcoming SError/RAS series that changes KVMs virtual-abort
>> code to specify an impdef ESR for this path.
> Before I remember Marc and you suggest me specify the an impdef ESR (set the vsesr_el2) in
> the userspace,

I pasted Marc's propose and your suggestion that set VSESR_EL2(specify
virtual SError syndrome) by the user space.
https://lkml.org/lkml/2017/3/20/441
https://lkml.org/lkml/2017/3/20/516


> now do you want to specify an impdef ESR in KVM instead of usrspace?
> if setting the vsesr_el2 in the KVM, whether user-space need to specify?
> May be we can combine the patches that specify an impdef ESR(set vsesr_el2) patch to one.
>

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from  userspace gengdongjiu <gengdongjiu@huawei.com> - 2017-09-27 13:20 +0200
  Re: [PATCH v6 6/7] KVM: arm64: allow get exception information from userspace gengdongjiu <gengdj.1984@gmail.com> - 2017-09-27 17:40 +0200

csiph-web