From: James Morse <james.morse@arm.com>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: rkrcmar@redhat.com, corbet@lwn.net, christoffer.dall@linaro.org,
marc.zyngier@arm.com, linux@armlinux.org.uk,
catalin.marinas@arm.com, rjw@rjwysocki.net, bp@alien8.de,
lenb@kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-acpi@vger.kernel.org,
devel@acpica.org, huangshaoyu@huawei.com, zhengxiang9@huawei.com
Subject: Re: [PATCH v11 0/4] set VSESR_EL2 by user space and support NOTIFY_SEI notification
Date: Tue, 10 Apr 2018 15:15:32 +0100 [thread overview]
Message-ID: <d94439b6-9b9a-9bd0-ddec-3bb63ede9461@arm.com> (raw)
In-Reply-To: <1523309796-36423-1-git-send-email-gengdongjiu@huawei.com>
Hi Dongjiu Geng,
On 09/04/18 22:36, Dongjiu Geng wrote:
> 1. Detect whether KVM can set set guest SError syndrome
> 2. Support to Set VSESR_EL2 and inject SError by user space.
> 3. Support live migration to keep SError pending state and VSESR_EL2 value.
> 4. ACPI 6.1 adds support for NOTIFY_SEI as a GHES notification mechanism, so support this
> notification in software, KVM or kernel ARCH code call handle_guest_sei() to let ACP driver
> to handle this notification.
Please don't post code during the merge-window, will this apply to v4.17-rc1? We
can't know until its tagged.
This series is doing two separate things, please split it into two series.
But on the ACPI front: I don't see how any OS can support your NOTIFY_SEI when
firmware is ignoring the normal world's PSTATE.A.
The latest lobe of that discussion was on the list here:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1611496.html
As it is, we would need to spot SError being delivered while SError is masked,
spray nasty messages about firmware being horrifically buggy, then panic(). For
a corrected error, this looks bad, but its preferable to letting firmware
silently overwrite the exception registers, causing linux to spin through the
vectors 'eret' with all exceptions masked.
I still think its best to wait for firmware that does the right thing.
Thanks,
James
next prev parent reply other threads:[~2018-04-10 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 21:36 Dongjiu Geng
2018-04-09 21:36 ` [PATCH v11 1/4] arm64: KVM: export the capability to set guest SError syndrome Dongjiu Geng
2018-04-10 14:15 ` James Morse
2018-04-12 12:55 ` gengdongjiu
2018-04-09 21:36 ` [PATCH v11 2/4] arm/arm64: KVM: Add KVM_GET/SET_VCPU_EVENTS Dongjiu Geng
2018-04-10 14:15 ` James Morse
2018-04-12 15:11 ` gengdongjiu
2018-04-09 21:36 ` [PATCH v11 3/4] ACPI / APEI: Add SEI notification type support for ARMv8 Dongjiu Geng
2018-04-09 21:36 ` [PATCH v11 4/4] arm64: handle NOTIFY_SEI notification by the APEI driver Dongjiu Geng
2018-04-10 14:15 ` James Morse [this message]
2018-04-12 6:09 ` [PATCH v11 0/4] set VSESR_EL2 by user space and support NOTIFY_SEI notification gengdongjiu
2018-04-12 16:14 ` James Morse
2018-04-19 4:09 ` 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=d94439b6-9b9a-9bd0-ddec-3bb63ede9461@arm.com \
--to=james.morse@arm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=corbet@lwn.net \
--cc=devel@acpica.org \
--cc=gengdongjiu@huawei.com \
--cc=huangshaoyu@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=rjw@rjwysocki.net \
--cc=rkrcmar@redhat.com \
--cc=zhengxiang9@huawei.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®