From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Cc: "Wei Liu" <wl@xen.org>,
solene@openbsd.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Demi Marie Obenour" <demi@invisiblethingslab.com>,
"Roger Pau Monne" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org,
"the arch/x86 maintainers" <x86@kernel.org>
Subject: Re: [Xen PATCH] x86/amd: do not expose HWCR.TscFreqSel to guests
Date: Wed, 13 Sep 2023 22:31:43 +0200 [thread overview]
Message-ID: <87sf7hzufk.ffs@tglx> (raw)
In-Reply-To: <fca202a8-2716-6ed1-c2ce-707deeddb3ab@citrix.com>
On Wed, Sep 13 2023 at 12:02, Andrew Cooper wrote:
> The PSTATE MSRs are entirely model specific, fully read/write, and the
> Enable bit is not an enable bit; its a "not valid yet" bit that firmware
> is required to adjust to be consistent across the coherency fabric.
>
> Linux is simply wrong with it's printk() under virt, and wants adjusting.
No objections from my side.
Thanks,
tglx
next prev parent reply other threads:[~2023-09-13 20:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 16:23 [PATCH] x86/amd: do not expose HWCR.TscFreqSel to guests Roger Pau Monne
2023-09-12 16:35 ` Andrew Cooper
2023-09-12 16:36 ` Andrew Cooper
2023-09-13 8:08 ` Roger Pau Monné
2023-09-13 10:11 ` Andrew Cooper
2023-09-13 6:18 ` Jan Beulich
2023-09-13 8:50 ` Roger Pau Monné
2023-09-13 11:02 ` [Xen PATCH] " Andrew Cooper
2023-09-13 13:37 ` Jan Beulich
2023-09-13 20:31 ` Thomas Gleixner [this message]
2023-09-13 7:50 ` [PATCH] " Roger Pau Monné
2023-09-13 10:50 ` Andrew Cooper
2023-09-13 13:27 ` Jan Beulich
2023-09-13 6:14 ` Jan Beulich
2023-09-13 8:20 ` Roger Pau Monné
2023-09-13 8:35 ` Jan Beulich
2023-09-13 9:16 ` Roger Pau Monné
2023-09-13 9:40 ` Jan Beulich
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=87sf7hzufk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=demi@invisiblethingslab.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=solene@openbsd.org \
--cc=wl@xen.org \
--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 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.