mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Babu Moger <babu.moger@amd.com>,
	Jim Mattson <jmattson@google.com>
Subject: Re: [PATCH] KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical
Date: Fri, 28 Feb 2025 15:40:32 -0800	[thread overview]
Message-ID: <174076298281.3738096.14978008039669090737.b4-ty@google.com> (raw)
In-Reply-To: <20250224174522.2363400-1-seanjc@google.com>

On Mon, 24 Feb 2025 09:45:22 -0800, Sean Christopherson wrote:
> Inject a #GP if the memory operand received by INVCPID is non-canonical.
> The APM clearly states that the intercept takes priority over all #GP
> checks except the CPL0 restriction.
> 
> Of course, that begs the question of how the CPU generates a linear
> address in the first place.  Tracing confirms that EXITINFO1 does hold a
> linear address, at least for 64-bit mode guests (hooray GS prefix).
> Unfortunately, the APM says absolutely nothing about the EXITINFO fields
> for INVPCID intercepts, so it's not at all clear what's supposed to
> happen.
> 
> [...]

Applied to kvm-x86 svm, thanks!

[1/1] KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical
      https://github.com/kvm-x86/linux/commit/d4b69c3d1471

--
https://github.com/kvm-x86/linux/tree/next

      reply	other threads:[~2025-02-28 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 17:45 Sean Christopherson
2025-02-28 23:40 ` 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=174076298281.3738096.14978008039669090737.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=babu.moger@amd.com \
    --cc=jmattson@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®