From: gengdongjiu <gengdongjiu@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>, <james.morse@arm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Zhaoshenglong <zhaoshenglong@huawei.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>, kvm-devel <kvm@vger.kernel.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <marc.zyngier@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
James Morse <james.morse@arm.com>,
Tyler Baicar <tbaicar@codeaurora.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Ingo Molnar" <mingo@kernel.org>, "bp@suse.de" <bp@suse.de>,
Shiju Jose <shiju.jose@huawei.com>,
"zjzhang@codeaurora.org" <zjzhang@codeaurora.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"lkml - Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
"John Garry" <john.garry@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
huangdaode <huangdaode@hisilicon.com>,
"Wangzhou (B)" <wangzhou1@hisilicon.com>,
Huangshaoyu <huangshaoyu@huawei.com>,
Wuquanming <wuquanming@huawei.com>,
Linuxarm <linuxarm@huawei.com>,
"Zhengqiang (turing)" <zhengqiang10@huawei.com>
Subject: Re: [PATCH v11 6/6] target-arm: kvm64: Handle SError interrupt for the guest OS
Date: Wed, 13 Sep 2017 15:52:14 +0800 [thread overview]
Message-ID: <5552cf68-b998-686b-8e7e-710399c2b014@huawei.com> (raw)
In-Reply-To: <CAFEAcA8J5wZ23kQypzcbUScUResjWnN6rDG0b0idD1rv7F5Fsw@mail.gmail.com>
On 2017/9/12 0:39, Peter Maydell wrote:
>>>> + return kvm_vcpu_ioctl(CPU(cpu), KVM_ARM_SEI, &syndrome);
>>> This looks odd. If we don't have the RAS extension why do we need to do anything at all here ?
>> This is because Qemu may need to support non-RAS extension as discussed with ARM James before.
>> That is to say host hardware CPU does not support RAS, but guest supports.
>> That is under discussion.
>> When host hardware supports RAS, specify the syndrome to a valid value, otherwise, set it to 0.
> If the guest CPU doesn't support the RAS extension then we have
> no mechanism for delivering it a notification about the
> memory problem at all, so setting the syndrome to anything
> doesn't make sense.
>
> I'm not sure what you should do in the case of "host
> supports telling us about a memory problem and has
> done so, but guest does not support being told about it",
> but I'm pretty sure it shouldn't be this.
Hi peter,
thanks for the comments.
in short, if the hardware CPU does not support RAS extension, do you think whether the Qemu or guest OS
needs to support RAS(generate APEI table / record CPER / Error recovery).
CC James,
Hi James,
you ever have below comments:
-----------------------------------------------------------------------
But you can use APEI in a guest on CPUs without the RAS extensions: the host may
signal memory errors to Qemu for any number of reasons.
------------------------------------------------------------------
in fact, I have a concern about it. If CPU without the RAS extension, the host should not deliver the sigbus.
in which case in your test that host still deliver sigbus without RAS?
next prev parent reply other threads:[~2017-09-13 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 15:17 gengdongjiu
2017-09-11 16:39 ` Peter Maydell
2017-09-13 7:52 ` gengdongjiu [this message]
2017-09-13 10:52 ` Peter Maydell
2017-09-13 11:51 ` gengdongjiu
-- strict thread matches above, loose matches on Subject: below --
2017-08-18 14:23 [PATCH v11 0/6] Add RAS virtualization support for armv8 SEA and SEI Dongjiu Geng
2017-08-18 14:23 ` [PATCH v11 6/6] target-arm: kvm64: Handle SError interrupt for the guest OS Dongjiu Geng
2017-09-05 17:50 ` Peter Maydell
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=5552cf68-b998-686b-8e7e-710399c2b014@huawei.com \
--to=gengdongjiu@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=devel@acpica.org \
--cc=edk2-devel@lists.01.org \
--cc=huangdaode@hisilicon.com \
--cc=huangshaoyu@huawei.com \
--cc=imammedo@redhat.com \
--cc=james.morse@arm.com \
--cc=john.garry@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tbaicar@codeaurora.org \
--cc=wangzhou1@hisilicon.com \
--cc=will.deacon@arm.com \
--cc=wuquanming@huawei.com \
--cc=zhaoshenglong@huawei.com \
--cc=zhengqiang10@huawei.com \
--cc=zjzhang@codeaurora.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
all inboxes | Powered by JetHome®