linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	Shuai Xue <xueshuai@linux.alibaba.com>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,  Hanjun Guo <guohanjun@huawei.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org,  linux-edac@vger.kernel.org,
	x86@kernel.org, justin.he@arm.com,  ardb@kernel.org,
	ying.huang@linux.alibaba.com, ashish.kalra@amd.com,
	 baolin.wang@linux.alibaba.com, tglx@linutronix.de,
	 dave.hansen@linux.intel.com, lenb@kernel.org, hpa@zytor.com,
	 robert.moore@intel.com, lvying6@huawei.com, xiexiuqi@huawei.com,
	 zhuo.song@linux.alibaba.com, sudeep.holla@arm.com,
	lpieralisi@kernel.org,  linux-acpi@vger.kernel.org,
	yazen.ghannam@amd.com, mark.rutland@arm.com,  mingo@redhat.com,
	robin.murphy@arm.com, Jonathan.Cameron@huawei.com,  bp@alien8.de,
	linux-arm-kernel@lists.infradead.org,
	 wangkefeng.wang@huawei.com, tanxiaofei@huawei.com,
	mawupeng1@huawei.com,  linmiaohe@huawei.com,
	naoya.horiguchi@nec.com, james.morse@arm.com,
	 tongtiangen@huawei.com, gregkh@linuxfoundation.org,
	jarkko@kernel.org
Subject: Re: [RESEND PATCH v18 1/2] ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered
Date: Tue, 15 Jul 2025 14:40:41 +0200	[thread overview]
Message-ID: <CAJZ5v0ikkHeopHQb2Gxr4GnW3rqtowpWu_DEa5ahLK6f2nHH9Q@mail.gmail.com> (raw)
In-Reply-To: <20250715140530.42c6bdc4@sal.lan>

On Tue, Jul 15, 2025 at 2:06 PM Mauro Carvalho Chehab
<mchehab+huawei@kernel.org> wrote:
>
> Em Mon, 14 Jul 2025 19:30:19 +0200
> "Rafael J. Wysocki" <rafael@kernel.org> escreveu:
>
> > Hi,
> >
> > On Mon, Jul 14, 2025 at 1:54 PM Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> > >
> > > 在 2025/7/1 21:56, Rafael J. Wysocki 写道:
> > > > On Tue, Jul 1, 2025 at 1:00 PM Shuai Xue <xueshuai@linux.alibaba.com> wrote:
> > > >>
> > > >>   >在 2025/4/28 23:23, Will Deacon 写道:
> > > >>   >> On Fri, Apr 25, 2025 at 09:10:09AM +0800, Shuai Xue wrote:
> > > >>   >>> 在 2025/4/25 09:00, Hanjun Guo 写道:
> > > >>   >>>> Call force_sig(SIGBUS) directly in ghes_do_proc() is not my favourite,
> > > >>   >>>> but I can bear that, please add
> > > >>   >>>>
> > > >>   >>>> Reviewed-by: Hanjun Guo <guohanjun@huawei.com>
> > > >>   >>>>
> > > >>   >>>> Thanks
> > > >>   >>>> Hanjun
> > > >>   >>>
> > > >>   >>> Thanks. Hanjun.
> > > >>   >>>
> > > >>   >>> @Rafael, @Catalin,
> > > >>   >>>
> > > >>   >>> Both patch 1 and 2 have reviewed-by tag from the arm64 ACPI
> > > >> maintainers, Hanjun,
> > > >>   >>> now. Are you happpy to pick and queue this patch set to acpi tree
> > > >> or arm tree?
> > > >>   >>
> > > >>   >> Since this primarily touches drivers/acpi/apei/ghes.c, I think it should
> > > >>   >> go via the ACPI tree and not the arm64 one.
> > > >>   >>
> > > >>   >> Will
> > > >>   >
> > > >>   >Hi, Will,
> > > >>   >
> > > >>   >Thank you for your confirmation :)
> > > >>   >
> > > >>   >@Rafael, do you have more comments on this patch set?
> > > >>   >
> > > >>   >Thanks you.
> > > >>   >
> > > >>   >Best Regards,
> > > >>   >Shuai
> > > >>
> > > >> Hi, all,
> > > >>
> > > >> Gentle ping.
> > > >>
> > > >> Does ACPI or APEI tree still active? Looking forward to any response.
> > > >
> > > > For APEI changes, you need an ACK from one of the reviewers listed in
> > > > the MAINTAINERS entry for APEI.
> > > >
> > > > Thanks!
> > >
> > > Hi, Rafael
> > >
> > > Sorry, I missed your email which goes in span (:
> > >
> > > ARM maintain @Catalin points that:
> > >
> > >  > James Morse is listed as reviewer of the ACPI APEI code but he's busy
> > >  > with resctrl/MPAM. Adding Lorenzo, Sudeep and Hanjun as arm64 ACPI
> > >  > maintainers, hopefully they can help.
> > >
> > > And Hanjun explictly gived his Reviewed-by tag in this thread, is that
> > > happy for you for merge?
> >
> > Not really.
> >
> > I need an ACK or R-by from a reviewer listed in the APEI entry in MAINTAINERS.
> >
> > If James Morse is not able to fill that role (and AFAICS he's not been
> > for quite some time now), I'd expect someone else to step up.

Hi Mauro,

> Rafael,
>
> If you want, I can step-up to help with APEI review. Besides my work
> with RAS/EDAC in the past, I'm doing some work those days adding
> APEI injection in QEMU those days (currently focused on ARM error
> injection via SEA and GPIO).

Thank you!

OK, let me send a MAINTAINERS update with a list of new APEI reviewers.


  reply	other threads:[~2025-07-15 13:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 11:20 [RESEND PATCH v18 0/2] ACPI: APEI: handle synchronous errors in task work Shuai Xue
2025-04-04 11:20 ` [RESEND PATCH v18 1/2] ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered Shuai Xue
2025-04-14 14:37   ` Hanjun Guo
2025-04-14 15:02     ` Shuai Xue
2025-04-18  7:48       ` Hanjun Guo
2025-04-18 12:35         ` Shuai Xue
2025-04-25  1:00           ` Hanjun Guo
2025-04-25  1:10             ` Shuai Xue
2025-04-28 15:23               ` Will Deacon
2025-05-14  1:35                 ` Shuai Xue
2025-07-01 11:00                 ` Shuai Xue
2025-07-01 13:56                   ` Rafael J. Wysocki
2025-07-14 11:54                     ` Shuai Xue
2025-07-14 17:30                       ` Rafael J. Wysocki
2025-07-15  2:03                         ` Shuai Xue
2025-07-15  2:46                         ` Hanjun Guo
2025-07-15 12:06                         ` Mauro Carvalho Chehab
2025-07-15 12:40                           ` Rafael J. Wysocki [this message]
2025-04-04 11:20 ` [RESEND PATCH v18 2/2] ACPI: APEI: handle synchronous exceptions in task work Shuai Xue
2025-04-14 14:48   ` Hanjun Guo
2025-04-14 14:56     ` Shuai Xue
2025-04-08  2:34 ` [RESEND PATCH v18 0/2] ACPI: APEI: handle synchronous errors " Hanjun Guo

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=CAJZ5v0ikkHeopHQb2Gxr4GnW3rqtowpWu_DEa5ahLK6f2nHH9Q@mail.gmail.com \
    --to=rafael@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=ashish.kalra@amd.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guohanjun@huawei.com \
    --cc=hpa@zytor.com \
    --cc=james.morse@arm.com \
    --cc=jarkko@kernel.org \
    --cc=justin.he@arm.com \
    --cc=lenb@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lpieralisi@kernel.org \
    --cc=lvying6@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=mawupeng1@huawei.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mingo@redhat.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=robert.moore@intel.com \
    --cc=robin.murphy@arm.com \
    --cc=sudeep.holla@arm.com \
    --cc=tanxiaofei@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=tongtiangen@huawei.com \
    --cc=tony.luck@intel.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=xiexiuqi@huawei.com \
    --cc=xueshuai@linux.alibaba.com \
    --cc=yazen.ghannam@amd.com \
    --cc=ying.huang@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).