public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Vasant Karasulli <vkarasulli@suse.de>
Cc: vsntk18@gmail.com, kvm@vger.kernel.org, pbonzini@redhat.com,
	 jroedel@suse.de, papaluri@amd.com, andrew.jones@linux.dev,
	 Varad Gautam <varad.gautam@suse.com>,
	Marc Orr <marcorr@google.com>
Subject: Re: [kvm-unit-tests PATCH v7 07/11] lib/x86: Move xsave helpers to lib/
Date: Thu, 6 Jun 2024 16:49:47 -0700	[thread overview]
Message-ID: <ZmJLG4zMq3KbHwPi@google.com> (raw)
In-Reply-To: <ZmIG3sNYe0C1jsXx@vasant-suse>

On Thu, Jun 06, 2024, Vasant Karasulli wrote:
> On Mi 05-06-24 09:04:04, Sean Christopherson wrote:
> > On Fri, Apr 19, 2024, vsntk18@gmail.com wrote:
> > > From: Vasant Karasulli <vkarasulli@suse.de>
> > >
> > > Processing CPUID #VC for AMD SEV-ES requires copying xcr0 into GHCB.
> > > Move the xsave read/write helpers used by xsave testcase to lib/x86
> > > to share as common code.
> >
> > This doesn't make any sense, processor.h _is_ common code.  And using
> > get_supported_xcr0(), which does CPUID, in a #VC handler is even more nonsensical.
> > Indeed, it's still used only by test_xsave() at the end of this series.
> >
> 
> The idea was to have xcr0 related declarations and definitions in the same place
> which were distributed across files. Does that make sense to you?  If not
> I will move back get_supported_xcr0() to where it was.

I don't necessarily disagree with that approach, but I don't think we need a
dedicated xsave.h, e.g. just move get_supported_xcr0() to processor.h.

  reply	other threads:[~2024-06-06 23:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 16:16 [kvm-unit-tests PATCH v7 00/11] Add #VC exception handling for AMD SEV-ES vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 01/11] x86: AMD SEV-ES: Setup #VC exception handler " vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 02/11] x86: Move svm.h to lib/x86/ vsntk18
2024-06-05 16:05   ` Sean Christopherson
2024-06-06 18:57     ` Vasant Karasulli
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 03/11] lib: Define unlikely()/likely() macros in compiler.h vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 04/11] lib: x86: Import insn decoder from Linux vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 05/11] x86: AMD SEV-ES: Pull related GHCB definitions and helpers " vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 06/11] x86: AMD SEV-ES: Prepare for #VC processing vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 07/11] lib/x86: Move xsave helpers to lib/ vsntk18
2024-06-05 16:04   ` Sean Christopherson
2024-06-06 18:58     ` Vasant Karasulli
2024-06-06 23:49       ` Sean Christopherson [this message]
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 08/11] x86: AMD SEV-ES: Handle CPUID #VC vsntk18
2024-06-05 16:07   ` Sean Christopherson
2024-06-06 18:59     ` Vasant Karasulli
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 09/11] x86: AMD SEV-ES: Handle MSR #VC vsntk18
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 10/11] x86: AMD SEV-ES: Handle IOIO #VC vsntk18
2024-06-05 16:08   ` Sean Christopherson
2024-06-06 19:01     ` Vasant Karasulli
2024-04-19 16:16 ` [kvm-unit-tests PATCH v7 11/11] x86: AMD SEV-ES: Handle string IO for " vsntk18

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=ZmJLG4zMq3KbHwPi@google.com \
    --to=seanjc@google.com \
    --cc=andrew.jones@linux.dev \
    --cc=jroedel@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=marcorr@google.com \
    --cc=papaluri@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=varad.gautam@suse.com \
    --cc=vkarasulli@suse.de \
    --cc=vsntk18@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox