From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, acme@kernel.org,
ak@linux.intel.com, mark.rutland@arm.com, luto@amacapital.net,
eranian@google.com, namhyung@kernel.org
Subject: Re: [PATCH V3 1/2] perf/x86: Move cpuc->running into P4 specific code
Date: Wed, 14 Apr 2021 14:22:15 +0200 [thread overview]
Message-ID: <YHbed9/VDTiDg+vt@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1618340250-29027-1-git-send-email-kan.liang@linux.intel.com>
Thanks for these Kan!
prev parent reply other threads:[~2021-04-14 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 18:57 [PATCH V3 1/2] perf/x86: Move cpuc->running into P4 specific code kan.liang
2021-04-13 18:57 ` [PATCH V3 2/2] perf/x86: Reset the dirty counter to prevent the leak for an RDPMC task kan.liang
2021-04-13 20:33 ` kernel test robot
2021-04-14 13:47 ` Liang, Kan
2021-04-13 23:41 ` kernel test robot
2021-04-14 0:34 ` Andy Lutomirski
2021-04-14 1:30 ` Liang, Kan
2021-04-14 13:51 ` Namhyung Kim
2021-04-14 14:27 ` Liang, Kan
2021-04-14 12:22 ` Peter Zijlstra [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=YHbed9/VDTiDg+vt@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@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