All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sohil Mehta <sohil.mehta@intel.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
	kvm@vger.kernel.org, x86@kernel.org,
	 Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	 Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	 "H . Peter Anvin" <hpa@zytor.com>, Shuah Khan <shuah@kernel.org>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	 Peter Zijlstra <peterz@infradead.org>,
	Kai Huang <kai.huang@intel.com>,
	 Fuad Tabba <fuad.tabba@linux.dev>, Chao Gao <chao.gao@intel.com>,
	 Yosry Ahmed <yosry@kernel.org>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	 David Matlack <dmatlack@google.com>,
	Bala-Vignesh-Reddy <reddybalavignesh9979@gmail.com>,
	 Kishen Maloor <kishen.maloor@intel.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>,
	 linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v4 4/7] KVM: VMX: Implement LASS violation check
Date: Wed, 16 Sep 2026 11:38:01 -0700	[thread overview]
Message-ID: <aqriCQTG7F73aEpX@google.com> (raw)
In-Reply-To: <f4fdef08-fdf0-4af8-bf59-07c48625b282@intel.com>

On Tue, Sep 15, 2026, Sohil Mehta wrote:
> On 9/15/2026 7:04 AM, Sean Christopherson wrote:
> > That said, I love Sohil's idea of adding a function comment.  Someting along the
> > lines of "The basic flow is this: <example>, but the actual behavior is far more
> > subtle due to many exceptions and edge cases".
> 
> Great, how about this?

LGTM.

> > /*
> >  * Check if an access violates LASS purely based on bit 63 of the linear address
> >  * and whether the access targets the "wrong" half of the address space. The
> >  * basic flow is straightforward:
> >  *
> >  *	if (exempt from LASS)
> >  *		no violation;
> >  *	else if (user access)
> >  *		violation when address is in the supervisor half;
> >  *	else
> >  *		violation when address is in the user half;
> >  *
> >  * but the actual behavior is far more subtle due to the many exceptions and
> >  * edge cases. For example, the implementation depends on which accesses are
> >  * exempt, what constitutes a user access, and how supervisor data accesses
> >  * differ from instruction fetches.
> >  */
> > bool vmx_is_lass_violation(struct kvm_vcpu *vcpu, gva_t gva,
> > 			   unsigned int size, unsigned int flags)
> 
> 
> 
> Sean, other than this, do you want to see any big change in the series?

Dunno, I haven't looked at anything else in the series, I just saw that I got
summoned :-)

It's on my list of things to review, but I'm behind on reviews this kernel cycle
for a variety of reasons.

> The sashiko complains are false-positives. There are a couple of nits to
> be addressed, and I need to change Binbin's SoBs into Reviewed-bys.
> Otherwise, I think the series (1-5) is getting ready to be picked up.
> 

  reply	other threads:[~2026-09-16 18:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  1:15 [PATCH v4 0/7] KVM: x86: Add LASS virtualization support Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 1/7] KVM: x86: Add an emulator flag to differentiate branch targets from fetches Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 2/7] KVM: x86: Use linear_read_system() to read the TSS I/O bitmap Sohil Mehta
2026-08-19  3:19   ` Binbin Wu
2026-08-19  5:03     ` Sohil Mehta
2026-08-19  5:21       ` H. Peter Anvin
2026-08-19  5:26       ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 3/7] KVM: x86: Add LASS violation checks during instruction emulation Sohil Mehta
2026-08-19  5:58   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 4/7] KVM: VMX: Implement LASS violation check Sohil Mehta
2026-08-06  1:52   ` sashiko-bot
2026-08-07  1:42     ` Sohil Mehta
2026-08-19  8:49   ` Binbin Wu
2026-09-14 17:43   ` Chang S. Bae
2026-09-15  5:10     ` Sohil Mehta
2026-09-15 14:04       ` Sean Christopherson
2026-09-16  0:12         ` Sohil Mehta
2026-09-16 18:38           ` Sean Christopherson [this message]
2026-09-16 21:49             ` Sohil Mehta
2026-08-06  1:15 ` [PATCH v4 5/7] KVM: x86: Virtualize LASS and advertise support to userspace Sohil Mehta
2026-08-19  9:01   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 6/7] KVM: selftests: Add coverage for LASS CPUID and CR4 handling Sohil Mehta
2026-08-20  6:01   ` Binbin Wu
2026-08-06  1:15 ` [PATCH v4 7/7] selftests/x86: Add a userspace test for LASS enforcement Sohil Mehta
2026-08-20  6:36   ` Binbin Wu
2026-09-15  3:22     ` Sohil Mehta
2026-09-14 18:21   ` Chang S. Bae
2026-09-15  3:16     ` Sohil Mehta
2026-08-26  3:50 ` [PATCH v4 0/7] KVM: x86: Add LASS virtualization support Kishen Maloor
2026-08-27  3:18 ` Chen, Farrah

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=aqriCQTG7F73aEpX@google.com \
    --to=seanjc@google.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dmatlack@google.com \
    --cc=fuad.tabba@linux.dev \
    --cc=hpa@zytor.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kai.huang@intel.com \
    --cc=kishen.maloor@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=reddybalavignesh9979@gmail.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=shuah@kernel.org \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@kernel.org \
    --cc=x86@kernel.org \
    --cc=yosry@kernel.org \
    /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.