From: Andrew Cooper <amc96@srcf.net>
To: Peter Zijlstra <peterz@infradead.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
tglx@linutronix.de, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, jgross@suse.com
Subject: Re: [PATCH] x86/smp: Factor out parts of native_smp_prepare_cpus()
Date: Tue, 9 Nov 2021 15:28:32 +0000 [thread overview]
Message-ID: <aef8093d-f7da-c8b4-ebf6-6053b50b77ba@srcf.net> (raw)
In-Reply-To: <YYqPd1c9HIQH9k/9@hirez.programming.kicks-ass.net>
On 09/11/2021 15:10, Peter Zijlstra wrote:
> On Mon, Nov 08, 2021 at 12:20:26PM -0500, Boris Ostrovsky wrote:
>>> But looking at those functions; there seems to be more spurious
>>> differences. For example, the whole sched_topology thing.
>>
>> I did look at that and thought this should be benign given that Xen PV
>> is not really topology-aware. I didn't see anything that would be a
>> cause for concern but perhaps you can point me to things I missed.
> And me not being Xen aware... What does Xen-PV guests see of the CPUID
> topology fields? Does it fully sanitize the CPUID data, or is it a clean
> pass-through from whatever CPU the vCPU happens to run on at the time?
That depends on hardware support (CPUID Faulting or not), version of Xen
(anything before Xen 4.7 is totally insane. Anything more recent is
only moderately insane), and whether the kernel asks via the enlightened
CPUID path or not.
On hardware lacking CPUID faulting, and for a kernel using
native_cpuid() where it ought to be using the PVOP, it sees the real
hardware value of the CPU it happens to be running on.
~Andrew
next prev parent reply other threads:[~2021-11-09 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 23:36 Boris Ostrovsky
2021-11-03 5:45 ` Juergen Gross
2021-11-08 15:11 ` Peter Zijlstra
2021-11-08 17:20 ` Boris Ostrovsky
2021-11-09 15:10 ` Peter Zijlstra
2021-11-09 15:21 ` Juergen Gross
2021-11-09 15:28 ` Andrew Cooper [this message]
2021-11-10 21:52 ` Josef Johansson
2021-11-11 10:15 ` Peter Zijlstra
2021-11-11 12:39 ` Josef Johansson
2021-11-11 12:22 ` [tip: sched/urgent] " tip-bot2 for Boris Ostrovsky
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=aef8093d-f7da-c8b4-ebf6-6053b50b77ba@srcf.net \
--to=amc96@srcf.net \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
Powered by JetHome