From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <mark.rutland@arm.com>, <will@kernel.org>
Cc: <lecopzer.chen@mediatek.com>, <acme@kernel.org>,
<akpm@linux-foundation.org>, <alexander.shishkin@linux.intel.com>,
<catalin.marinas@arm.com>, <davem@davemloft.net>,
<jolsa@redhat.com>, <jthierry@redhat.com>,
<keescook@chromium.org>, <kernelfans@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <masahiroy@kernel.org>,
<matthias.bgg@gmail.com>, <maz@kernel.org>, <mcgrof@kernel.org>,
<mingo@redhat.com>, <namhyung@kernel.org>,
<nixiaoming@huawei.com>, <peterz@infradead.org>,
<pmladek@suse.com>, <sparclinux@vger.kernel.org>,
<sumit.garg@linaro.org>, <wangqing@vivo.com>,
<yj.chiang@mediatek.com>
Subject: RE: [PATCH v7 0/6] Support hld delayed init based on Pseudo-NMI for arm64
Date: Sat, 3 Sep 2022 17:45:23 +0800 [thread overview]
Message-ID: <20220903094523.16002-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <20220903093415.15850-1-lecopzer.chen@mediatek.com>
Hi Will, Mark
Sorry for bothering you, this need to be reviewed by ARM Perf maintainer,
could you please help review this pathset or comment about it?
Thanks a lot.
> Hi Will, Mark
>
> Could you help review arm parts of this patchset, please?
>
> For the question mention in both [1] and [2],
>
> > I'd still like Mark's Ack on this, as the approach you have taken doesn't
> > really sit with what he was suggesting.
> >
> > I also don't understand how all the CPUs get initialised with your patch,
> > since the PMU driver will be initialised after SMP is up and running.
>
> The hardlock detector utilizes the softlockup_start_all() to start all
> the cpu on watchdog_allowed_mask, which will do watchdog_nmi_enable()
> that registers perf event on each CPUs.
> Thus we simply need to retry lockup_detector_init() in a single cpu which
> will reconfig and call to softlockup_start_all().
>
> Also, the CONFIG_HARDLOCKUP_DETECTOR_PERF selects SOFTLOCKUP_DETECTOR,
> IMO, this shows that hardlockup detector supports from softlockup.
>
>
> > We should know whether pNMIs are possible once we've completed
> > setup_arch() (and possibly init_IRQ()), long before SMP, so so I reckon
> > we should have all the information available once we get to
> > lockup_detector_init(), even if that requires some preparatory rework.
>
> Hardlockup depends on PMU driver , I think the only way is moving
> pmu driver at setup_arch() or any point which is earlier than
> lockup_detector_init(), and I guess we have to reorganize the architecture
> of arm PMU.
>
> The retry function should benifit all the arch/ not only for arm64.
> Any arch who needs to probe its pmu as module can use this without providing
> a chance to mess up the setup order.
>
>
> Please let me know if you have any concern about this, thank you
>
>
> [1] https://lore.kernel.org/all/CAFA6WYPPgUvHCpN5=EpJ2Us5h5uVWCbBA59C-YwYQX2ovyVeEw@mail.gmail.com/
> [2] https://lore.kernel.org/linux-arm-kernel/20210419170331.GB31045@willie-the-truck/
>
>
next prev parent reply other threads:[~2022-09-03 9:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 9:34 [PATCH v7 0/6] Support hld delayed init based on Pseudo-NMI for Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 1/6] kernel/watchdog: remove WATCHDOG_DEFAULT Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 2/6] kernel/watchdog: change watchdog_nmi_enable() to void Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 3/6] kernel/watchdog_hld: Ensure CPU-bound context when creating hardlockup detector event Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 4/6] kernel/watchdog: Adapt the watchdog_hld interface for async model Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 5/6] arm64: add hw_nmi_get_sample_period for preparation of lockup detector Lecopzer Chen
2022-09-03 9:34 ` [PATCH v7 6/6] arm64: Enable perf events based hard " Lecopzer Chen
2022-09-04 22:57 ` kernel test robot
2022-09-03 9:45 ` Lecopzer Chen [this message]
2022-11-07 15:18 ` [PATCH v7 0/6] Support hld delayed init based on Pseudo-NMI for Will Deacon
2023-05-04 22:41 ` Doug Anderson
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=20220903094523.16002-1-lecopzer.chen@mediatek.com \
--to=lecopzer.chen@mediatek.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=jolsa@redhat.com \
--cc=jthierry@redhat.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sparclinux@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--cc=wangqing@vivo.com \
--cc=will@kernel.org \
--cc=yj.chiang@mediatek.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).