All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yu Zhang <yu.c.zhang@linux.intel.com>
Cc: Jun Miao <jun.miao@intel.com>, pbonzini@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Update the version number of SDM in comments
Date: Thu, 15 Jun 2023 07:36:52 -0700	[thread overview]
Message-ID: <ZIsiBCYB+18KG1XR@google.com> (raw)
In-Reply-To: <20230615091819.fzr67tevfxmcbnqo@linux.intel.com>

On Thu, Jun 15, 2023, Yu Zhang wrote:
> On Thu, Jun 15, 2023 at 04:06:24PM +0800, Jun Miao wrote:
> > A little optimized update version number of SDM and corresponding
> > public date, making it more accurate to retrieve.
> > 
> > Signed-off-by: Jun Miao <jun.miao@intel.com>
> > ---
> >  arch/x86/kvm/lapic.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> > index d7639d126e6c..4c5493e08d2e 100644
> > --- a/arch/x86/kvm/lapic.c
> > +++ b/arch/x86/kvm/lapic.c
> > @@ -2260,7 +2260,7 @@ static int apic_mmio_write(struct kvm_vcpu *vcpu, struct kvm_io_device *this,
> >  	/*
> >  	 * APIC register must be aligned on 128-bits boundary.
> >  	 * 32/64/128 bits registers must be accessed thru 32 bits.
> > -	 * Refer SDM 8.4.1
> 
> I would suggest just remove this line.

+1, and clean up the other part too?  The line about 32/64/128 bits registers is
also flawed; there are no 128-bit registers, just 256-bit registers.  I see no
reason to precisely call out the sizes.  And this would be a good opportunity to
call out that KVM allows smaller reads, but not smaller writes.

E.g. something like this?

	/*
	 * APIC registers must be aligned on 128-bit boundaries, and must be
	 * written using 32-bit stores regardless of the register size.  Note,
	 * KVM allows smaller 8-bit and 16-bit loads to be compatible with
	 * guest software (some microarchitectures support such loads, even
	 * though only 32-bit loads are architecturally guaranteed to work).
	 */

> And maybe, add "According to Intel SDM, " at the beginning of the comments.

Nah, not necessary.  It's implied that KVM is implementing architecturally behavior
unless otherwise stated.  And this isn't Intel specific code, e.g. the APM (hopefully)
says the same thing.

      reply	other threads:[~2023-06-15 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  8:06 [PATCH] KVM: x86: Update the version number of SDM in comments Jun Miao
2023-06-15  9:18 ` Yu Zhang
2023-06-15 14:36   ` Sean Christopherson [this message]

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=ZIsiBCYB+18KG1XR@google.com \
    --to=seanjc@google.com \
    --cc=jun.miao@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=yu.c.zhang@linux.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.