From: Qi Zheng <zhengqi.arch@bytedance.com>
To: peterz@infradead.org, keescook@chromium.org, jpoimboe@kernel.org,
dave.hansen@linux.intel.com, bp@alien8.de, mingo@redhat.com,
tglx@linutronix.de, rostedt@goodmis.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] some fixes and cleanups for x86
Date: Fri, 7 Apr 2023 11:47:23 +0800 [thread overview]
Message-ID: <58d0903b-0081-6a0a-e199-b90af19eb6a2@bytedance.com> (raw)
In-Reply-To: <20230330081552.54178-1-zhengqi.arch@bytedance.com>
On 2023/3/30 16:15, Qi Zheng wrote:
> Hi all,
>
> This series uses arch_stack_walk() to fix false positives of KASAN and
> avoid open-coding of unwind logic.
Gentle ping. Any comments or suggestions? :)
>
> This series is based on next-20230330.
>
> Comments and suggestions are welcome.
>
> Thanks,
> Qi
>
> Qi Zheng (2):
> x86: make profile_pc() use arch_stack_walk()
> x86: make __get_wchan() use arch_stack_walk()
>
> arch/x86/kernel/process.c | 22 ++++++++++++----------
> arch/x86/kernel/time.c | 36 +++++++++++++++++-------------------
> 2 files changed, 29 insertions(+), 29 deletions(-)
>
--
Thanks,
Qi
prev parent reply other threads:[~2023-04-07 3:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:15 Qi Zheng
2023-03-30 8:15 ` [PATCH 1/2] x86: make profile_pc() use arch_stack_walk() Qi Zheng
2023-04-08 4:56 ` Josh Poimboeuf
2023-04-08 5:26 ` Qi Zheng
2023-03-30 8:15 ` [PATCH 2/2] x86: make __get_wchan() " Qi Zheng
2023-04-08 5:08 ` Josh Poimboeuf
2023-04-08 5:36 ` Qi Zheng
2023-04-08 22:12 ` Josh Poimboeuf
2023-04-09 6:30 ` Qi Zheng
2023-04-12 5:20 ` Josh Poimboeuf
2023-04-12 7:10 ` Qi Zheng
2023-04-12 13:15 ` Peter Zijlstra
2023-04-12 13:23 ` Peter Zijlstra
2023-04-12 17:24 ` Qi Zheng
2023-04-07 3:47 ` Qi Zheng [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=58d0903b-0081-6a0a-e199-b90af19eb6a2@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®