From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Takahiro Itazuri <itazur@amazon.com>,
dave.hansen@linux.intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
tglx@linutronix.de, x86@kernel.org, zulinx86@gmail.com
Subject: Re: [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests
Date: Tue, 7 Mar 2023 11:28:26 -0800 [thread overview]
Message-ID: <ZAeQWre1PM7vsWd3@google.com> (raw)
In-Reply-To: <20230307185811.GEZAeJQ8U+NYySH8up@fat_crate.local>
On Tue, Mar 07, 2023, Borislav Petkov wrote:
> On Tue, Mar 07, 2023 at 10:49:22AM -0800, Sean Christopherson wrote:
> > I don't see what such a rule buys us beyond complexity and, IMO, unnecessary
> > maintenance burden. As Paolo pointed out, when there's an existing word, the
>
> Maybe I wasn't clear enough - I don't mind existing words. What I mind
> is adding new ones only for KVM's sake.
Ah, gotcha. We're on the same page then. Thanks!
next prev parent reply other threads:[~2023-03-07 19:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 21:05 [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests Takahiro Itazuri
2023-02-27 21:05 ` [PATCH 1/2] x86/cpufeatures: Add AMD-specific IBRS bits Takahiro Itazuri
2023-02-27 21:05 ` [PATCH 2/2] KVM: x86: Propagate AMD-specific IBRS related bits Takahiro Itazuri
2023-02-27 21:40 ` [PATCH 0/2] KVM: x86: Propagate AMD-specific IBRS bits to guests Borislav Petkov
2023-02-28 18:13 ` Takahiro Itazuri
2023-02-28 19:24 ` Borislav Petkov
2023-02-28 19:41 ` Takahiro Itazuri
2023-02-28 20:45 ` Borislav Petkov
2023-02-28 22:24 ` Takahiro Itazuri
2023-02-28 22:50 ` Borislav Petkov
2023-03-06 21:16 ` Sean Christopherson
2023-03-06 21:25 ` Paolo Bonzini
2023-03-06 21:44 ` Borislav Petkov
2023-03-06 21:47 ` Paolo Bonzini
2023-03-06 21:54 ` Borislav Petkov
2023-03-07 18:49 ` Sean Christopherson
2023-03-07 18:58 ` Borislav Petkov
2023-03-07 19:28 ` Sean Christopherson [this message]
2023-03-07 19:55 ` Borislav Petkov
2023-03-06 21:31 ` Paolo Bonzini
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=ZAeQWre1PM7vsWd3@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=itazur@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zulinx86@gmail.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.