mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 John Stultz <jstultz@google.com>,
	Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH] KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop
Date: Fri, 14 Feb 2025 16:18:45 -0800	[thread overview]
Message-ID: <Z6_dZTbQbgr2iY6Q@google.com> (raw)
In-Reply-To: <1db73488-4095-4ac1-ad10-139615981de2@redhat.com>

On Sat, Feb 15, 2025, Paolo Bonzini wrote:
> On 2/15/25 01:06, Sean Christopherson wrote:
> > On Fri, Feb 14, 2025, Paolo Bonzini wrote:
> > > Queued, thanks.
> > 
> > Drat, I was too slow today.  I applied and pushed this to "kvm-x86 fixes" and
> > linux-next (as of yesterday), along with a few other things, I just haven't sent
> > out the "thanks" yet (got sidetracked).
> > 
> > If you want to grab those, here's a semi-impromptu pull request.  Otherwise I'll
> > just drop this particular commit.
> 
> I had "KVM: nSVM: Enter guest mode before initializing nested NPT MMU" on my
> list, but not the others.
> 
> I'll just pull these, thanks.

Heh, while you're here, here's combined pull request for the selftests changes
that missed 6.14 due to the pmu_counters_test snafumi[1][2]?

I'm a-ok if you want to hold off until 6.15.  I have them sitting in a separate
branch (selftests_6.14), and don't anticipate conflicts, so it's no trouble to
carry them until the next merge window.

[1] https://lore.kernel.org/all/Z6qN3wPXH4cbRzLP@google.com
[2] https://lore.kernel.org/all/20250117010718.2328467-5-seanjc@google.com

---
The following changes since commit 10b2c8a67c4b8ec15f9d07d177f63b563418e948:

  Merge tag 'kvm-x86-fixes-6.13-rcN' of https://github.com/kvm-x86/linux into HEAD (2024-12-22 12:59:33 -0500)

are available in the Git repository at:

  https://github.com/kvm-x86/linux.git tags/kvm-x86-selftests-6.14-2

for you to fetch changes up to 54108e73344480c3e5f3799129970009f52c59f4:

  KVM: selftests: Print out the actual Top-Down Slots count on failure (2025-02-12 08:34:56 -0800)

----------------------------------------------------------------
KVM selftests changes for 6.14:

 - Misc cleanups and prep work.

 - Annotate _no_printf() with "printf" so that pr_debug() statements are
   checked by the compiler for default builds (and pr_info() when QUIET).

 - Attempt to whack the last LLC references/misses mole in the Intel PMU
   counters test by adding a data load and doing CLFLUSH{OPT} on the data
   instead of the code being executed.  The theory is that modern Intel CPUs
   have learned new code prefetching tricks that bypass the PMU counters.

 - Fix a flaw in the Intel PMU counters test where it asserts that an event is
   counting correctly without actually knowing what the event counts on the
   underlying hardware.

----------------------------------------------------------------
Chen Ni (1):
      KVM: selftests: Remove unneeded semicolon

Colton Lewis (2):
      KVM: selftests: Fix typos in x86's PMU counter test's macro variable use
      KVM: selftests: Add defines for AMD PMU CPUID features and properties

Isaku Yamahata (1):
      KVM: selftests: Add printf attribute to _no_printf()

Sean Christopherson (7):
      KVM: selftests: Use data load to trigger LLC references/misses in Intel PMU
      KVM: selftests: Add helpers for locally (un)blocking IRQs on x86
      KVM: selftests: Make Intel arch events globally available in PMU counters test
      KVM: selftests: Only validate counts for hardware-supported arch events
      KVM: selftests: Remove dead code in Intel PMU counters test
      KVM: selftests: Drop the "feature event" param from guest test helpers
      KVM: selftests: Print out the actual Top-Down Slots count on failure

 tools/testing/selftests/kvm/access_tracking_perf_test.c |   2 +-
 tools/testing/selftests/kvm/include/test_util.h         |   2 +-
 tools/testing/selftests/kvm/include/x86/processor.h     |  47 +++++++++++++++++++++++++++++++++
 tools/testing/selftests/kvm/x86/hyperv_ipi.c            |   6 +++--
 tools/testing/selftests/kvm/x86/pmu_counters_test.c     | 158 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----------------------------------------------
 tools/testing/selftests/kvm/x86/svm_int_ctl_test.c      |   5 +---
 tools/testing/selftests/kvm/x86/ucna_injection_test.c   |   2 +-
 tools/testing/selftests/kvm/x86/xapic_ipi_test.c        |   3 ++-
 tools/testing/selftests/kvm/x86/xapic_state_test.c      |   4 +--
 tools/testing/selftests/kvm/x86/xen_shinfo_test.c       |   5 +---
 10 files changed, 151 insertions(+), 83 deletions(-)

  reply	other threads:[~2025-02-15  0:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25  1:18 Sean Christopherson
2025-02-14 23:40 ` Paolo Bonzini
2025-02-15  0:06   ` Sean Christopherson
2025-02-15  0:08     ` Paolo Bonzini
2025-02-15  0:18       ` Sean Christopherson [this message]
2025-02-15  0:50 ` Sean Christopherson

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=Z6_dZTbQbgr2iY6Q@google.com \
    --to=seanjc@google.com \
    --cc=jmattson@google.com \
    --cc=jstultz@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.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

all inboxes | Powered by JetHome®