mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, tglx@linutronix.de, bp@alien8.de,
	acme@kernel.org, namhyung@kernel.org, irogers@google.com,
	linux-kernel@vger.kernel.org, ak@linux.intel.com,
	eranian@google.com
Subject: Re: [PATCH V7 1/6] perf: Save PMU specific data in task_struct
Date: Wed, 12 Mar 2025 11:34:30 -0400	[thread overview]
Message-ID: <8303cd57-cbc3-4d36-b544-d894f59e1535@linux.intel.com> (raw)
In-Reply-To: <20250312135749.GD9968@noisy.programming.kicks-ass.net>



On 2025-03-12 9:57 a.m., Peter Zijlstra wrote:
> On Wed, Mar 12, 2025 at 02:54:23PM +0100, Peter Zijlstra wrote:
>>> The whole patch set was posted several years ago. But it's buried in the
>>> LKML without merging. I've received several requests recently to fix the
>>> LBR issue with system-wide events. Rebase and repost it.
>>>
>>> - Rebase on top of Peter's perf/core branch.
>>
>> That branch is older than tip/perf/core, as such things don't apply
>> anymore :/
> 
> I've pushed out a new queue/perf/core, based on tip/perf/core + your
> patch from yesterday.
> 

Thanks. I will rebase the patch set.

Thanks,
Kan


      reply	other threads:[~2025-03-12 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 13:04 kan.liang
2025-03-12 13:04 ` [PATCH V7 2/6] perf: attach/detach PMU specific data kan.liang
2025-03-12 13:04 ` [PATCH V7 3/6] perf: Supply task information to sched_task() kan.liang
2025-03-12 13:04 ` [PATCH V7 4/6] perf/x86/lbr: Fix shorter LBRs call stacks for the system-wide mode kan.liang
2025-03-12 13:04 ` [PATCH V7 5/6] perf/x86: Remove swap_task_ctx() kan.liang
2025-03-12 13:04 ` [PATCH V7 6/6] perf: Clean up pmu specific data kan.liang
2025-03-12 13:54 ` [PATCH V7 1/6] perf: Save PMU specific data in task_struct Peter Zijlstra
2025-03-12 13:57   ` Peter Zijlstra
2025-03-12 15:34     ` 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=8303cd57-cbc3-4d36-b544-d894f59e1535@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=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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®