From: Peter Zijlstra <peterz@infradead.org>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Naman Jain <namjain@linux.microsoft.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Steve Wahl <steve.wahl@hpe.com>,
Saurabh Singh Sengar <ssengar@linux.microsoft.com>,
srivatsa@csail.mit.edu, Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v3] sched/topology: Enable topology_span_sane check only for debug builds
Date: Wed, 5 Feb 2025 11:16:00 +0100 [thread overview]
Message-ID: <20250205101600.GC7145@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <0835864f-6dc5-430d-91c0-b5605007d9d2@amd.com>
On Wed, Feb 05, 2025 at 03:43:54PM +0530, K Prateek Nayak wrote:
> Hello Peter,
>
> Thank you for the background!
>
> On 2/5/2025 3:25 PM, Peter Zijlstra wrote:
> > On Wed, Feb 05, 2025 at 03:18:24PM +0530, K Prateek Nayak wrote:
> >
> > > Have there been any reports on an x86 system / VM where
> > > topology_span_sane() was tripped?
> >
> > At the very least Intel SNC 'feature' tripped it at some point. They
> > figured it made sense to have the LLC span two nodes.
> >
> > But I think there were some really dodgy VMs too.
> >
> > But yeah, its not been often. But basically dodgy BIOS/VM data can mess
> > up things badly enough for it to trip.
>
> Has it ever happened without tripping the topology_sane() check first
> on the x86 side?
That I can't remember, sorry :/
next prev parent reply other threads:[~2025-02-05 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:47 [PATCH v3] sched/topology: Enable topology_span_sane check only for debug builds Naman Jain
2025-02-05 7:20 ` K Prateek Nayak
2025-02-05 7:23 ` Naman Jain
2025-02-10 9:53 ` Naman Jain
2025-02-05 9:48 ` K Prateek Nayak
2025-02-05 9:55 ` Peter Zijlstra
2025-02-05 10:13 ` K Prateek Nayak
2025-02-05 10:16 ` Peter Zijlstra [this message]
2025-02-06 9:10 ` K Prateek Nayak
2025-02-06 9:47 ` Naman Jain
2025-02-06 10:19 ` K Prateek Nayak
2025-02-06 10:55 ` Naman Jain
2025-02-06 15:24 ` Valentin Schneider
2025-02-06 15:30 ` Steve Wahl
2025-02-06 17:18 ` Naman Jain
2025-02-07 2:44 ` K Prateek Nayak
2025-02-11 5:52 ` Shrikanth Hegde
2025-02-11 7:06 ` Naman Jain
2025-02-11 10:56 ` K Prateek Nayak
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=20250205101600.GC7145@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=namjain@linux.microsoft.com \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=ssengar@linux.microsoft.com \
--cc=stable@vger.kernel.org \
--cc=steve.wahl@hpe.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.