Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: "Baicar, Tyler" <tbaicar@codeaurora.org>
To: Shiju Jose <shiju.jose@huawei.com>,
	"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"rkrcmar@redhat.com" <rkrcmar@redhat.com>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>,
	"robert.moore@intel.com" <robert.moore@intel.com>,
	"lv.zheng@intel.com" <lv.zheng@intel.com>,
	"nkaje@codeaurora.org" <nkaje@codeaurora.org>,
	"zjzhang@codeaurora.org" <zjzhang@codeaurora.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"james.morse@arm.com" <james.morse@arm.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	eun.taik.lee@samsung.com
Subject: Re: [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support
Date: Fri, 3 Mar 2017 15:43:46 -0700	[thread overview]
Message-ID: <e1578c9f-7595-9705-9a5a-5811cf6c8513@codeaurora.org> (raw)
In-Reply-To: <86258A5CC0A3704780874CF6004BA8A62DCAD116@lhreml502-mbs>

Hello Shiju,


On 3/3/2017 8:34 AM, Shiju Jose wrote:
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c index
>> b2d57fc..403277b 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@ -602,6 +602,24 @@ static const char *fault_name(unsigned int esr)  }
>>
>>   /*
>> + * Handle Synchronous External Aborts that occur in a guest kernel.
>> + */
>> +int handle_guest_sea(unsigned long addr, unsigned int esr) {
>> +	/*
>> +	 * synchronize_rcu() will wait for nmi_exit(), so no need to
>> +	 * rcu_read_lock().
>> +	 */
>> +	if(IS_ENABLED(HAVE_ACPI_APEI_SEA)) {
> IS_ENABLED(HAVE_ACPI_APEI_SEA) to be changed to IS_ENABLED(ACPI_APEI_SEA) same
> as in the patch "acpi: apei: handle SEA notification type for ARMv8"?
>
Good catch, I guess my FW still triggers the SCI interrupt as well as 
replays the SEA to kernel which is why I still get into the GHES handling :)

Thanks,
Tyler

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

      reply	other threads:[~2017-03-03 22:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 21:21 [PATCH V11 00/10] Add UEFI 2.6 and ACPI 6.1 updates for RAS on ARM64 Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 01/10] acpi: apei: read ack upon ghes record consumption Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 02/10] ras: acpi/apei: cper: generic error data entry v3 per ACPI 6.1 Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 03/10] efi: parse ARM processor error Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 04/10] arm64: exception: handle Synchronous External Abort Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 06/10] acpi: apei: panic OS with fatal error status block Tyler Baicar
2017-02-21 21:21 ` [PATCH V11 07/10] efi: print unrecognized CPER section Tyler Baicar
     [not found] ` <1487712121-16688-1-git-send-email-tbaicar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-02-21 21:21   ` [PATCH V11 05/10] acpi: apei: handle SEA notification type for ARMv8 Tyler Baicar
2017-03-01  7:42     ` Xie XiuQi
2017-03-01 19:22       ` Baicar, Tyler
2017-02-21 21:21   ` [PATCH V11 08/10] ras: acpi / apei: generate trace event for unrecognized CPER section Tyler Baicar
2017-02-21 21:22 ` [PATCH V11 09/10] trace, ras: add ARM processor error trace event Tyler Baicar
2017-02-21 21:22 ` [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support Tyler Baicar
2017-02-24 10:42   ` James Morse
2017-02-27 11:31     ` gengdongjiu
2017-02-28 19:43     ` Baicar, Tyler
2017-03-06 10:28       ` James Morse
2017-03-06 14:00         ` Baicar, Tyler
     [not found]   ` <1487712121-16688-11-git-send-email-tbaicar-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-02-25  7:15     ` Xiongfeng Wang
2017-02-27 13:58       ` James Morse
2017-02-28  6:25         ` Xiongfeng Wang
2017-02-28 13:21           ` James Morse
2017-03-01  2:31             ` Xiongfeng Wang
2017-03-02  9:39               ` Marc Zyngier
2017-03-06  3:38                 ` Xiongfeng Wang
2017-03-06  1:28         ` gengdongjiu
2017-03-22  2:46         ` Xiongfeng Wang
     [not found]           ` <6eee7a67-808e-8712-2ec2-593eac52d921-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-03-22 11:14             ` James Morse
2017-03-22 12:08               ` Xie XiuQi
2017-03-03 15:34   ` Shiju Jose
2017-03-03 22:43     ` Baicar, Tyler [this message]

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=e1578c9f-7595-9705-9a5a-5811cf6c8513@codeaurora.org \
    --to=tbaicar@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eun.taik.lee@samsung.com \
    --cc=james.morse@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lv.zheng@intel.com \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=nkaje@codeaurora.org \
    --cc=pbonzini@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=rkrcmar@redhat.com \
    --cc=robert.moore@intel.com \
    --cc=shiju.jose@huawei.com \
    --cc=will.deacon@arm.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