public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Miguel Ruiz <miguelies.ruiz@gmail.com>,
	ravi.bangoria@amd.com, tglx@linutronix.de,
	thomas.lendacky@amd.com
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, xin@zytor.com,
	tony.luck@intel.com, pawan.kumar.gupta@linux.intel.com,
	andriy.shevchenko@linux.intel.com, jgross@suse.com,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	christian@heusel.eu, Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <seanjc@google.com>
Subject: Re: [REGRESSION][BISECTED] Some applications under Windows 11 libvirt VM crash since commit 408eb7417a92c5354c7be34f7425b305dfe30ad9
Date: Wed, 5 Mar 2025 15:51:22 -0800	[thread overview]
Message-ID: <e5f56fd2-b2e2-48c1-bb3d-e00b61807893@intel.com> (raw)
In-Reply-To: <7a212431-5320-464b-a357-507fa6511586@intel.com>

On 3/5/25 15:42, Dave Hansen wrote:
> I'm also cc'ing the KVM folks. I don't actually know how the #GP from
> the split lock detection will manifest to KVM guests. I'm kinda
> surprised it crashes the guest app and doesn't do anything more noisy.

I've got my wires crossed somewhere. It's not a #GP, it's an #AC.


  reply	other threads:[~2025-03-05 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMEKE0Hd3S0-25afhWQhNNitbc7njp0ftO+Y3QmgS6CyFQh4ww@mail.gmail.com>
2025-03-05 23:42 ` [REGRESSION][BISECTED] Some applications under Windows 11 libvirt VM crash since commit 408eb7417a92c5354c7be34f7425b305dfe30ad9 Dave Hansen
2025-03-05 23:51   ` Dave Hansen [this message]
2025-03-06  0:10     ` 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=e5f56fd2-b2e2-48c1-bb3d-e00b61807893@intel.com \
    --to=dave.hansen@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=christian@heusel.eu \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miguelies.ruiz@gmail.com \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=pbonzini@redhat.com \
    --cc=ravi.bangoria@amd.com \
    --cc=regressions@lists.linux.dev \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=xin@zytor.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