From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Jiaqi Yan <jiaqiyan@google.com>, "Luck, Tony" <tony.luck@intel.com>
Cc: "Hsiao, Duen-wen" <duenwen@google.com>,
"rientjes@google.com" <rientjes@google.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"shy828301@gmail.com" <shy828301@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v1 0/3] Introduce per NUMA node memory error statistics
Date: Thu, 19 Jan 2023 04:52:32 +0000 [thread overview]
Message-ID: <20230119045215.GA3515247@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <CACw3F50Pwh_ym=6+Px9kCxbfHYyAqkn3rXxntVqp46Pf7s+OdA@mail.gmail.com>
On Wed, Jan 18, 2023 at 03:33:00PM -0800, Jiaqi Yan wrote:
> Awesome, thanks Tony, I will correct my cover letter.
>
> On Wed, Jan 18, 2023 at 9:51 AM Luck, Tony <tony.luck@intel.com> wrote:
> >
> > > Oh, maybe SRAO signaled via MCE calls memory_failure() with these
> > > async code paths?
> > >
> > > 1. __mc_scan_banks => mce_log => mce_gen_pool_add + irq_work_queue(mce_irq_work)
> > >
> > > 2. mce_irq_work_cb => mce_schedule_work => schedule_work(&mce_work)
> > >
> > > 3. mce_work => mce_gen_pool_process =>
> > > blocking_notifier_call_chain(&x86_mce_decoder_chain, 0, mce)
> > > => mce_uc_nb => uc_decode_notifier => memory_failure
> >
> > Yes. That's right. Both SRAO (#MC) and UCNA (CMCI) will follow that path.
> > So memory_failure() is called from the kthread context for that notifier.
I misunderstood the behavior of UCNA (CMCI), so thank you for confirming
the behaviors, both of you.
- Naoya Horiguchi
prev parent reply other threads:[~2023-01-19 4:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 19:38 Jiaqi Yan
2023-01-16 19:39 ` [PATCH v1 1/3] mm: memory-failure: Add memory failure stats to sysfs Jiaqi Yan
2023-01-16 20:15 ` Andrew Morton
2023-01-17 9:14 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-19 21:16 ` Jiaqi Yan
2023-01-17 9:02 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-16 19:39 ` [PATCH v1 2/3] mm: memory-failure: Bump memory failure stats to pglist_data Jiaqi Yan
2023-01-16 20:16 ` Andrew Morton
2023-01-17 9:03 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-18 23:05 ` Jiaqi Yan
2023-01-19 6:40 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-19 18:05 ` Jiaqi Yan
2023-01-16 19:39 ` [PATCH v1 3/3] mm: memory-failure: Document memory failure stats Jiaqi Yan
2023-01-16 20:13 ` [PATCH v1 0/3] Introduce per NUMA node memory error statistics Andrew Morton
2023-01-16 21:52 ` Jiaqi Yan
2023-01-17 9:18 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-17 17:51 ` Jiaqi Yan
2023-01-17 18:33 ` Luck, Tony
2023-01-18 17:31 ` Jiaqi Yan
2023-01-18 17:50 ` Luck, Tony
2023-01-18 23:33 ` Jiaqi Yan
2023-01-19 4:52 ` HORIGUCHI NAOYA(堀口 直也) [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=20230119045215.GA3515247@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=duenwen@google.com \
--cc=jiaqiyan@google.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@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