Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Mathias Krause <minipli@grsecurity.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org,  Andrew Jones <andrew.jones@linux.dev>
Subject: Re: [kvm-unit-tests PATCH v3 00/20] x86: Better backtraces for leaf functions
Date: Wed, 27 May 2026 08:41:12 -0700	[thread overview]
Message-ID: <ahcQmNWSroRQj5B0@google.com> (raw)
In-Reply-To: <09aad595-c4ef-4cc1-8aaf-e2300fe5a619@grsecurity.net>

On Thu, May 21, 2026, Mathias Krause wrote:
> On 21.05.26 12:48, Paolo Bonzini wrote:
> > On Thu, May 21, 2026 at 12:35 PM Mathias Krause <minipli@grsecurity.net> wrote:
> >>> I'm applying patches 1-18, adding the last two give
> >>
> >> Looks like Sean already integrated them into
> >> https://github.com/kvm-x86/kvm-unit-tests, including the fixups that
> >> came up during review.
> > 
> > Oopsie. I've merged manually everything from there up to commit
> > 0ddb0873cf4f1bd584c0981836778b795bab94f0.
> > 
> > Let's post what's left as a new submission to the mailing list.
> 
> In this case, Sean, can you please fold in the fixup for bbe76fbda4e1
> ("x86: Prevent realmode test code instrumentation with nop-mcount") I
> posted at [1]?

Given that the last two patches are yours, and that I can barely follow what the
patches are doing, can you post a new standalone mini-series with those two patches,
and whatever changes are needed to make 'em work?

> The cc-option test for -mfentry is probably too conservative but there
> were versions of gcc between 8 and 9 that did support -mnop-mcount but
> not -mfentry and the latter was, apparently, not needed until recently.
> 
> [1]
> https://lore.kernel.org/kvm/092d0688-0c8d-4b82-bb62-abeb26845df3@grsecurity.net/
> 
> Thanks,
> Mathias

  reply	other threads:[~2026-05-27 15:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 21:04 [kvm-unit-tests PATCH v3 00/20] x86: Better backtraces for leaf functions Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 01/20] x86/vmx: Drop unused SYSENTER "support" in nested VMX infrastructure Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 02/20] x86/vmx: Drop unused guest_regs " Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 03/20] x86/svm: Sort (and swap) GPRs by their index, not alphabetically Sean Christopherson
2026-05-21 16:51   ` Yosry Ahmed
2026-05-21 18:42     ` Sean Christopherson
2026-05-21 18:47       ` Yosry Ahmed
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 04/20] x86: Dedup guest/host context switch of registers across SVM and VMX Sean Christopherson
2026-05-19 21:51   ` Mathias Krause
2026-05-20  1:30     ` Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 05/20] x86/virt: Use macro shenanigans to get reg offsets when swapping guest/host regs Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 06/20] x86/virt: Track "guest regs" using per-CPU variable Sean Christopherson
2026-05-19 21:52   ` Mathias Krause
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 07/20] x86/svm: Don't VMLOAD/VMSAVE "guest" state around VMRUN Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 08/20] x86/vmx: Use separate VMCSes for BSP vs. AP in INIT test Sean Christopherson
2026-05-19 21:54   ` Mathias Krause
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 09/20] x86/vmx: Swap GPRs after checking "launched" status Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 10/20] x86/vmx: Track VMCS "launched" state per-CPU Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 11/20] x86/vmx: Track "is this CPU in guest mode" per-CPU Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 12/20] x86/vmx: Communicate hypercalls via RAX, not a global field Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 13/20] x86/vmx: Initialize test stage in SIPI test *before* launching AP thread Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 14/20] x86/kvmclock: Replace spaces with tabs Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 15/20] x86/kvmclock: Skip kvmclock test when not running on KVM with CLOCKSOURCE2 Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 16/20] x86/vmx: Tag "struct vmx_msr_entry" as needing to be 16-byte aligned Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 17/20] x86/smp: Align the stack to a 16-byte boundary when invoking SMP function calls Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 18/20] x86/vmx: Write to KVM's WALL_CLOCK MSR via VM-Entry load list sync in SIPI test Sean Christopherson
2026-05-14 21:04 ` [kvm-unit-tests PATCH v3 19/20] x86: Better backtraces for leaf functions Sean Christopherson
2026-05-14 21:05 ` [kvm-unit-tests PATCH v3 20/20] x86: Prevent realmode test code instrumentation with nop-mcount Sean Christopherson
2026-05-19 22:15 ` [kvm-unit-tests PATCH v3 00/20] x86: Better backtraces for leaf functions Mathias Krause
2026-05-21  9:24 ` Paolo Bonzini
2026-05-21 10:14   ` Paolo Bonzini
2026-05-21 10:35   ` Mathias Krause
2026-05-21 10:48     ` Paolo Bonzini
2026-05-21 12:19       ` Mathias Krause
2026-05-27 15:41         ` Sean Christopherson [this message]
2026-05-27 18:25           ` Mathias Krause

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=ahcQmNWSroRQj5B0@google.com \
    --to=seanjc@google.com \
    --cc=andrew.jones@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=minipli@grsecurity.net \
    --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