From: gengdongjiu@huawei.com (gengdongjiu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] arm/arm64: signal SIBGUS and inject SEA Error
Date: Wed, 10 May 2017 20:37:59 +0800 [thread overview]
Message-ID: <10cdbd75-2b89-c816-e688-91f111687819@huawei.com> (raw)
In-Reply-To: <20170510122055.GE28721@cbox>
Hi Christoffer,
On 2017/5/10 20:20, Christoffer Dall wrote:
> On Wed, May 10, 2017 at 05:15:04PM +0800, gengdongjiu wrote:
>> Thanks James's explanation.
>>
>> Hi Christoffer,
>>
>> On 2017/5/9 22:28, James Morse wrote:
>>> Hi Christoffer,
>>>
>>> On 08/05/17 18:54, Christoffer Dall wrote:
>>>> On Mon, May 08, 2017 at 06:28:02PM +0100, James Morse wrote:
>>>> I must admit I am losing track of exactly what this proposed API was
>>>> supposed to do.
>>>
>>> There are two, and we keep jumping between them!
>>> This is about two notification methods APEI has for arm64, 'SEA' and 'SEI'.
>>>
>>> SEA is synchronous and looks like a data abort. Qemu/kvmtool can inject these
>>> today using the KVM_GET/SET_ONE_REG API whenever it wants to.
>>>
>>> SEI uses SError, is asynchronous and can be masked. In addition these need to be
>>> consumed/synchronised by the ESB instruction, even when executed by a guest.
>>> Hardware has the necessary bits to drive all this, we need to expose an API to
>>> drive it.
>>>
>>> (I try to spell them out each time so I don't confuse SEI with something
>>> synchronous!)
>>>
>>>
>>> This patch was about SEA. I think you've answered our question:
>>
>> we are talking about the SEA(synchronous data abort) injection two methods:
>>
>> (1)change vcpu registers in the Qemu/kvmtools and using the KVM_GET/SET_ONE_REG API to set.
>
> Yes, if this is possible, why would you want something more?
we will use this method.
>
>> (2)using existed in-kernel API "kvm_inject_dabt" to inject through IOCTL command from Qemu.
>>
>
> I'm not really going to consider this, because "use internal API from
> userspace" doesn't work.
>
> So this should be:
>
> (2) Introduce a new API to do X.
you can ignore the second method, now we will not use it.
>
> I still think you know what my preference is; use the existing API if at
> all possible.
>
> Thanks,
> -Christoffer
>
> .
>
next prev parent reply other threads:[~2017-05-10 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMj-D2BGTDKpOcMu2ip41_MTTj8VDwvs59Ds7yvLHcD8PeQzhg@mail.gmail.com>
2017-05-05 12:31 ` [PATCH v3 3/3] arm/arm64: signal SIBGUS and inject SEA Error gengdongjiu
2017-05-12 17:24 ` James Morse
2017-05-21 8:24 ` gengdongjiu
2017-05-08 17:28 ` James Morse
2017-05-08 17:54 ` Christoffer Dall
2017-05-09 14:28 ` James Morse
2017-05-10 9:15 ` gengdongjiu
2017-05-10 12:20 ` Christoffer Dall
2017-05-10 12:37 ` gengdongjiu [this message]
2017-05-10 8:44 ` gengdongjiu
2017-05-12 17:25 ` James Morse
2017-05-21 9:23 ` gengdongjiu
2017-04-30 5:37 [PATCH v3 1/3] arm64: kvm: support kvmtool to detect RAS extension feature Dongjiu Geng
2017-04-30 5:37 ` [PATCH v3 3/3] arm/arm64: signal SIBGUS and inject SEA Error Dongjiu Geng
2017-05-02 15:41 ` James Morse
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=10cdbd75-2b89-c816-e688-91f111687819@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).