All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Yang Weijiang <weijiang.yang@intel.com>,
	Manali Shukla <manali.shukla@amd.com>,
	Jim Mattson <jmattson@google.com>
Subject: Re: [kvm-unit-tests GIT PULL] x86: Fixes, cleanups, and new sub-tests
Date: Mon, 25 Jul 2022 20:35:06 +0000	[thread overview]
Message-ID: <Yt7+epRAIL7EK2jj@google.com> (raw)
In-Reply-To: <Yt7LJZpmF3ddJJnk@google.com>

On Mon, Jul 25, 2022, Sean Christopherson wrote:
> On Sat, Jul 23, 2022, Sean Christopherson wrote:
> > On Thu, Jul 21, 2022, Sean Christopherson wrote:
> > > Please pull/merge a pile of x86 cleanups and fixes, most of which have been
> > > waiting for review/merge for quite some time.  The only non-trivial changes that
> > > haven't been posted are the massaged version of the PMU cleanup patches.
> > > 
> > > Note, the very last commit will fail spectacularly on kvm/queue due to a KVM
> > > bug: https://lore.kernel.org/all/20220607213604.3346000-4-seanjc@google.com.
> > > 
> > > Other than that, tested on Intel and AMD, both 64-bit and 32-bit.
> > 
> > Argh, don't pull this.
> > 
> > Commit b89a09f ("x86: Provide a common 64-bit AP entrypoint for EFI and non-EFI")
> > broke the SVM tests on Rome.  I'll look into it next week and spin a new version.
> 
> The APIC needs to be "reset" to put it back into xAPIC, otherwise pre_boot_apic_id()
> will return garbage when `svm_init_startup_test` is run and x2APIC is supported.

And of course that breaks EFI.  Posted a small series to play nice with x2APIC and
provide a segue into the UEFI changes.

  reply	other threads:[~2022-07-25 20:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 21:13 [kvm-unit-tests GIT PULL] x86: Fixes, cleanups, and new sub-tests Sean Christopherson
2022-07-23  1:14 ` Sean Christopherson
2022-07-25 16:56   ` Sean Christopherson
2022-07-25 20:35     ` Sean Christopherson [this message]
2022-11-14 21:03 Sean Christopherson
2022-11-17 13:52 ` 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=Yt7+epRAIL7EK2jj@google.com \
    --to=seanjc@google.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=manali.shukla@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=weijiang.yang@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.