From: Valentin Schneider <vschneid@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ajay Kaher <akaher@vmware.com>,
Eric Vaughn <ervaughn@linux.microsoft.com>,
Sishuai Gong <sishuai.system@gmail.com>,
Uros Bizjak <ubizjak@gmail.com>,
Yue Haibing <yuehaibing@huawei.com>,
Zhang Zekun <zhangzekun11@huawei.com>,
Zheng Yejian <zhengyejian1@huawei.com>
Subject: Re: [GIT PULL] tracing: Updates for 6.6
Date: Fri, 01 Sep 2023 14:19:02 +0200 [thread overview]
Message-ID: <xhsmho7imaxxl.mognet@vschneid.remote.csb> (raw)
In-Reply-To: <20230901074400.349d5c41@rorschach.local.home>
On 01/09/23 07:44, Steven Rostedt wrote:
> On Fri, 01 Sep 2023 11:20:31 +0200
> Valentin Schneider <vschneid@redhat.com> wrote:
>> > Tracing updates for 6.6:
>> >
>> > User visible changes:
>> >
>> > - Added a way to easier filter with cpumasks:
>> > # echo 'cpumask & CPUS{17-42}' > /sys/kernel/tracing/events/ipi_send_cpumask/filter
>> >
>>
>> It looks like the patches included are from v2 of [1], which still had some
>> (small) issues to fix. I have addressed these in [2], but I haven't sent
>> this out yet as I'm still working on the context_tracking/vmalloc part of
>> the series.
>>
>> I'm happy to send just the tracing bits, if that helps - or just send the
>> deltas as separate fixes, whatever makes it easier.
>
> I put these patches into linux-next for a while, so I'm not going to
> rebase them. Can you send delta patches on top of this. This shouldn't
> stop this pull request.
>
Noted, I'll get on with this.
>>
>> Apologies for not bringing this up when the patches were picked up in [3],
>> I've only just come back from PTO/moving abroad and have started catching
>> up.
>
> I'm still trying to get home from my PTO, which I spent in Tampa and
> was suppose to fly home on Tuesday. But they closed the airport in
> preparation for Idalia, which forced my wife and I to hunker down in a
> hotel room for the last few days :-p (we are now in a to hotel room in
> Syracuse, and are about to drive home).
>
Sounds like you've had an "interesting" journey :)
> -- Steve
next prev parent reply other threads:[~2023-09-01 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 15:56 Steven Rostedt
2023-09-01 9:20 ` Valentin Schneider
2023-09-01 11:44 ` Steven Rostedt
2023-09-01 12:19 ` Valentin Schneider [this message]
2023-09-01 23:41 ` pr-tracker-bot
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=xhsmho7imaxxl.mognet@vschneid.remote.csb \
--to=vschneid@redhat.com \
--cc=akaher@vmware.com \
--cc=ervaughn@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sishuai.system@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=yuehaibing@huawei.com \
--cc=zhangzekun11@huawei.com \
--cc=zhengyejian1@huawei.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
all inboxes | Powered by JetHome®