From: Sean Christopherson <seanjc@google.com>
To: Kai Huang <kai.huang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>,
"robert.hu@linux.intel.com" <robert.hu@linux.intel.com>,
Chao Gao <chao.gao@intel.com>
Subject: Re: [PATCH v2 0/4] x86: Add test cases for LAM
Date: Thu, 6 Apr 2023 09:09:54 -0700 [thread overview]
Message-ID: <ZC7sQLdYpweORB6o@google.com> (raw)
In-Reply-To: <9896a0bf26e48dab853049f40733df5bb0e287a1.camel@intel.com>
On Thu, Apr 06, 2023, Huang, Kai wrote:
> On Sun, 2023-03-19 at 16:22 +0800, Binbin Wu wrote:
> > Intel Linear-address masking (LAM) [1], modifies the checking that is applied to
> > *64-bit* linear addresses, allowing software to use of the untranslated address
> > bits for metadata.
> >
> > The patch series add test cases for LAM:
> >
>
> I think you should just merge this series to the patchset which enables LAM
> feature?
No, please keep them separate. A lore link in the KUT series is more than
sufficient, and even that isn't really necesary. b4 and other tooling get
confused by series that contain patches for two (or more) different repositories,
i.e. posting everything in one bundle makes my life harder, not easier.
next prev parent reply other threads:[~2023-04-06 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 8:22 [PATCH v2 0/4] x86: Add test cases for LAM Binbin Wu
2023-03-19 8:22 ` [PATCH v2 1/4] x86: Allow setting of CR3 LAM bits if LAM supported Binbin Wu
2023-03-19 8:22 ` [PATCH v2 2/4] x86: Add test case for LAM_SUP Binbin Wu
2023-04-06 3:50 ` Chao Gao
2023-04-10 15:33 ` Binbin Wu
2023-03-19 8:22 ` [PATCH v2 3/4] x86: Add test cases for LAM_{U48,U57} Binbin Wu
2023-03-19 8:22 ` [PATCH v2 4/4] x86: Add test case for INVVPID with LAM Binbin Wu
2023-03-19 8:32 ` [PATCH v2 0/4] x86: Add test cases for LAM Binbin Wu
2023-04-06 11:39 ` Huang, Kai
2023-04-06 16:09 ` Sean Christopherson [this message]
2023-04-12 10:08 ` Huang, Kai
2023-04-10 15:24 ` Binbin Wu
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=ZC7sQLdYpweORB6o@google.com \
--to=seanjc@google.com \
--cc=binbin.wu@linux.intel.com \
--cc=chao.gao@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=robert.hu@linux.intel.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 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.