mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Tyler Baicar <tbaicar@codeaurora.org>,
	catalin.marinas@arm.com, will.deacon@arm.com, lenb@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	punit.agrawal@arm.com,
	"Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>
Subject: Re: [PATCH V2] arm64: kconfig: allow support for memory failure handling
Date: Wed, 22 Feb 2017 12:43:42 +0100	[thread overview]
Message-ID: <20170222114342.tz5wmnynwjos44fd@pd.tnic> (raw)
In-Reply-To: <4367727.rNzyOA836A@aspire.rjw.lan>

On Wed, Feb 22, 2017 at 01:53:54AM +0100, Rafael J. Wysocki wrote:
> [+ Boris]
> 
> On Tuesday, February 21, 2017 04:45:23 PM Tyler Baicar wrote:
> > From: "Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>
> > 
> > If ACPI_APEI and MEMORY_FAILURE is configured, select
> > ACPI_APEI_MEMORY_FAILURE. This enables memory failure recovery
> > when such memory failure is reported through ACPI APEI. APEI
> > (ACPI Platform Error Interfaces) provides a means for the
> > platform to convey error information to the kernel.
> > 
> > Declare ARCH_SUPPORTS_MEMORY_FAILURE, as arm64 does support
> > memory failure recovery attempt.
> > 
> > Signed-off-by: Jonathan (Zhixiong) Zhang <zjzhang@codeaurora.org>
> > Signed-off-by: Tyler Baicar <tbaicar@codeaurora.org>
> > ---
> >  arch/arm64/Kconfig        | 1 +
> >  drivers/acpi/apei/Kconfig | 1 +
> >  2 files changed, 2 insertions(+)
> > 
> > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> > index 1117421..61e0bb0 100644
> > --- a/arch/arm64/Kconfig
> > +++ b/arch/arm64/Kconfig
> > @@ -15,6 +15,7 @@ config ARM64
> >  	select ARCH_HAS_SG_CHAIN
> >  	select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
> >  	select ARCH_USE_CMPXCHG_LOCKREF
> > +	select ARCH_SUPPORTS_MEMORY_FAILURE
> >  	select ARCH_SUPPORTS_ATOMIC_RMW
> >  	select ARCH_SUPPORTS_NUMA_BALANCING
> >  	select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
> > diff --git a/drivers/acpi/apei/Kconfig b/drivers/acpi/apei/Kconfig
> > index b0140c8..6d9a812 100644
> > --- a/drivers/acpi/apei/Kconfig
> > +++ b/drivers/acpi/apei/Kconfig
> > @@ -9,6 +9,7 @@ config ACPI_APEI
> >  	select MISC_FILESYSTEMS
> >  	select PSTORE
> >  	select UEFI_CPER
> > +	select ACPI_APEI_MEMORY_FAILURE if MEMORY_FAILURE

Yap, looks ok to me: we're basically enabling
ghes_handle_memory_failure() to queue a memory address at fault for
possibly offlining on arm64. And since the arch supports it...

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

      reply	other threads:[~2017-02-22 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 23:45 Tyler Baicar
2017-02-22  0:53 ` Rafael J. Wysocki
2017-02-22 11:43   ` Borislav Petkov [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=20170222114342.tz5wmnynwjos44fd@pd.tnic \
    --to=bp@suse.de \
    --cc=catalin.marinas@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=punit.agrawal@arm.com \
    --cc=rjw@rjwysocki.net \
    --cc=tbaicar@codeaurora.org \
    --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

all inboxes | Powered by JetHome®