From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <kernelfans@gmail.com>
Cc: <acme@kernel.org>, <akpm@linux-foundation.org>,
<alexander.shishkin@linux.intel.com>, <catalin.marinas@arm.com>,
<jolsa@redhat.com>, <keescook@chromium.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <mark.rutland@arm.com>,
<masahiroy@kernel.org>, <maz@kernel.org>, <mingo@redhat.com>,
<namhyung@kernel.org>, <peterz@infradead.org>, <pmladek@suse.com>,
<samitolvanen@google.com>, <santosh@fossix.org>,
<sumit.garg@linaro.org>, <wangqing@vivo.com>, <will@kernel.org>,
<yj.chiang@mediatek.com>, <lecopzer.chen@mediatek.com>
Subject: Re: [PATCHv3 0/4] watchdog_hld cleanup and async model for arm64
Date: Mon, 17 Jan 2022 18:19:10 +0800 [thread overview]
Message-ID: <20220117101910.14999-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <20211014024155.15253-1-kernelfans@gmail.com>
Hi Pingfan,
Is this thread sill in progress?
We are looking for the upstream solution for ARM64 Hardlockup detector.
I'd appreciate it if someone keep working on it,
if not, I can take over it.
thanks!
-Lecopzer
next prev parent reply other threads:[~2022-01-17 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 2:41 [PATCHv3 0/4] watchdog_hld cleanup and async model for arm64 Pingfan Liu
2021-10-14 2:41 ` [PATCHv3 1/4] kernel/watchdog: trival cleanups Pingfan Liu
2021-10-14 2:41 ` [PATCHv3 2/4] kernel/watchdog_hld: Ensure CPU-bound context when creating hardlockup detector event Pingfan Liu
2021-10-14 2:41 ` [PATCHv3 3/4] kernel/watchdog: Adapt the watchdog_hld interface for async model Pingfan Liu
2021-10-14 2:41 ` [PATCHv3 4/4] arm64: Enable perf events based hard lockup detector Pingfan Liu
2022-01-17 10:19 ` Lecopzer Chen [this message]
2022-01-24 1:02 ` [PATCHv3 0/4] watchdog_hld cleanup and async model for arm64 Pingfan Liu
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=20220117101910.14999-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=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=samitolvanen@google.com \
--cc=santosh@fossix.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