From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Sean Christopherson <seanjc@google.com>
Cc: <kvm@vger.kernel.org>, <pbonzini@redhat.com>,
<linux-kernel@vger.kernel.org>, <yang.zhong@intel.com>
Subject: Re: [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component
Date: Thu, 25 Aug 2022 13:45:22 -0700 [thread overview]
Message-ID: <e52f26d4-c52a-e20d-7bc0-663bb4979827@intel.com> (raw)
In-Reply-To: <YwehLNws0WBNRDgN@google.com>
On 8/25/2022 9:19 AM, Sean Christopherson wrote:
>
> Adding new uAPI and new exports to eliminate one line of userspace code is not a
> good tradeoff. Am I missing something? This really seems like solution looking
> for a problem.
Well, then that's your call.
Yeah, that simplification is really minor. With this, I would rather
think KVM wants enforcement before relaying the request to the host.
That enforcement is unthinkable without supported_xcr0. But it looks
like userspace is somehow trusted here for KVM.
Thanks,
Chang
next prev parent reply other threads:[~2022-08-25 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 23:14 [RFC PATCH 0/2] KVM: x86: Add a new attribute to control dynamic XSTATE components Chang S. Bae
2022-08-23 23:14 ` [RFC PATCH 1/2] KVM: x86: Add a new system attribute for dynamic XSTATE component Chang S. Bae
2022-08-24 21:42 ` Sean Christopherson
2022-08-24 22:49 ` Chang S. Bae
2022-08-25 16:19 ` Sean Christopherson
2022-08-25 20:45 ` Chang S. Bae [this message]
2022-08-25 21:54 ` Sean Christopherson
2022-08-23 23:14 ` [RFC PATCH 2/2] selftests: kvm: Use the KVM API to enable dynamic XSTATE features Chang S. Bae
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=e52f26d4-c52a-e20d-7bc0-663bb4979827@intel.com \
--to=chang.seok.bae@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yang.zhong@intel.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.