public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, tglx@linutronix.de,
	bp@alien8.de, linux-kernel@vger.kernel.org, eranian@google.com,
	vitaly.slobodskoy@intel.com, namhyung@kernel.org,
	ak@linux.intel.com
Subject: Re: [PATCH V4 1/6] perf: Save PMU specific data in task_struct
Date: Fri, 21 May 2021 11:54:38 -0400	[thread overview]
Message-ID: <6acc7ffe-926a-86a7-edde-3833fb2ca53f@linux.intel.com> (raw)
In-Reply-To: <YKdgLP0l7+7LVhSs@hirez.programming.kicks-ass.net>



On 5/21/2021 3:24 AM, Peter Zijlstra wrote:
> I'm replying to the whole thing squashed, because I couldn't make sense
> of the individual patches much.

Thanks for the detailed comments. The optimization suggestions would 
make the codes much simpler and more efficient.
I will modify the codes based on your suggestions and do more tests.

Thanks,
Kan

      reply	other threads:[~2021-05-21 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 15:06 [PATCH V4 1/6] perf: Save PMU specific data in task_struct kan.liang
2021-05-19 15:06 ` [PATCH V4 2/6] perf: attach/detach PMU specific data kan.liang
2021-05-19 15:06 ` [PATCH V4 3/6] perf: Supply task information to sched_task() kan.liang
2021-05-19 15:06 ` [PATCH V4 4/6] perf/x86/lbr: Fix shorter LBRs call stacks for the system-wide mode kan.liang
2021-05-19 15:06 ` [PATCH V4 5/6] perf/x86: Remove swap_task_ctx() kan.liang
2021-05-19 15:06 ` [PATCH V4 6/6] perf: Clean up pmu specific data kan.liang
2021-05-21  7:24 ` [PATCH V4 1/6] perf: Save PMU specific data in task_struct Peter Zijlstra
2021-05-21 15:54   ` Liang, Kan [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=6acc7ffe-926a-86a7-edde-3833fb2ca53f@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vitaly.slobodskoy@intel.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