From: Libo Chen <libo.chen@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"mgorman@suse.de" <mgorman@suse.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"tj@kernel.org" <tj@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"llong@redhat.com" <llong@redhat.com>,
"kprateek.nayak@amd.com" <kprateek.nayak@amd.com>,
"raghavendra.kt@amd.com" <raghavendra.kt@amd.com>,
"yu.c.chen@intel.com" <yu.c.chen@intel.com>,
"tim.c.chen@intel.com" <tim.c.chen@intel.com>,
"vineethr@linux.ibm.com" <vineethr@linux.ibm.com>,
Chris Hyser <chris.hyser@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"mkoutny@suse.com" <mkoutny@suse.com>,
Dhaval Giani <Dhaval.Giani@amd.com>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] sched/numa: Add tracepoint that tracks the skipping of numa balancing due to cpuset memory pinning
Date: Wed, 23 Apr 2025 16:50:15 +0000 [thread overview]
Message-ID: <720D1AD7-112F-462F-9ECF-A060670D62D4@oracle.com> (raw)
In-Reply-To: <20250423121219.15d5c2ec@gandalf.local.home>
> On Apr 23, 2025, at 9:12 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Wed, 23 Apr 2025 16:05:44 +0000
> Libo Chen <libo.chen@oracle.com> wrote:
>
>> Also wondering if we can fail the build in this scenario so it will be easier to
>> catch this bug at the build time.
>
> return -EPONYS ;-)
>
> I wish. It's hard enough to catch this at runtime.
>
Correct me if I'm wrong but can you disallow any passed-in pointers to be
dereferenced when TP_printk() is executed? This is something you can check
at the build time, right?
Libo
> -- Steve
next prev parent reply other threads:[~2025-04-23 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 19:15 [PATCH v3 0/2] sched/numa: Skip VMA scanning on memory pinned Libo Chen
2025-04-17 19:15 ` [PATCH v3 1/2] sched/numa: Skip VMA scanning on memory pinned to one NUMA node via cpuset.mems Libo Chen
2025-04-19 11:16 ` Chen, Yu C
2025-04-22 22:20 ` Libo Chen
2025-04-22 23:27 ` Chen, Yu C
2025-04-17 19:15 ` [PATCH v3 2/2] sched/numa: Add tracepoint that tracks the skipping of numa balancing due to cpuset memory pinning Libo Chen
2025-04-23 15:34 ` Steven Rostedt
2025-04-23 16:05 ` Libo Chen
2025-04-23 16:12 ` Steven Rostedt
2025-04-23 16:50 ` Libo Chen [this message]
2025-04-23 16:56 ` Steven Rostedt
2025-04-23 16:57 ` Steven Rostedt
2025-04-23 18:22 ` Libo Chen
2025-04-17 20:12 ` [PATCH v3 0/2] sched/numa: Skip VMA scanning on memory pinned Andrew Morton
2025-04-17 21:07 ` Libo Chen
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=720D1AD7-112F-462F-9ECF-A060670D62D4@oracle.com \
--to=libo.chen@oracle.com \
--cc=Dhaval.Giani@amd.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris.hyser@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mkoutny@suse.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@intel.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vineethr@linux.ibm.com \
--cc=yu.c.chen@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
all inboxes | Powered by JetHome®