From: Dave Hansen <dave.hansen@intel.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Jiaxi Chen <jiaxi.chen@linux.intel.com>,
Kim Phillips <kim.phillips@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86: KVM: Add feature flag for AMD's FsGsKernelGsBaseNonSerializing
Date: Tue, 3 Oct 2023 20:27:37 -0700 [thread overview]
Message-ID: <dfdba4e2-371c-db18-6989-541f802a0783@intel.com> (raw)
In-Reply-To: <CALMp9eR+Qudg++J_dmY_SGbM_kr=GQcRRcjuUxtm9rfaC_qeXQ@mail.gmail.com>
On 10/3/23 19:44, Jim Mattson wrote:
> I'm a little surprised at the pushback, TBH. Are you implying that
> there is some advantage to *not* passing this bit through?
I'm not really trying to push back. I'm honestly just curious. Linux
obviously doesn't cat about the bit. So is this for some future Linux
or some other OS?
next prev parent reply other threads:[~2023-10-04 3:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 0:20 [PATCH] x86: KVM: Add feature flag for AMD's FsGsKernelGsBaseNonSerializing Jim Mattson
2023-10-04 0:57 ` Dave Hansen
2023-10-04 2:44 ` Jim Mattson
2023-10-04 3:27 ` Dave Hansen [this message]
2023-10-04 4:24 ` Jim Mattson
2023-10-04 7:58 ` Borislav Petkov
2023-10-04 20:29 ` Jim Mattson
2023-10-05 16:22 ` Jim Mattson
2023-10-05 16:35 ` Dave Hansen
2023-10-05 16:41 ` Jim Mattson
2023-10-05 16:51 ` Paolo Bonzini
2023-10-05 17:52 ` Dave Hansen
2023-10-05 16:38 ` Paolo Bonzini
2023-10-05 17:06 ` Jim Mattson
2023-10-05 17:14 ` Paolo Bonzini
2023-10-05 17:27 ` Jim Mattson
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=dfdba4e2-371c-db18-6989-541f802a0783@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jiaxi.chen@linux.intel.com \
--cc=jmattson@google.com \
--cc=kim.phillips@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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