From: Shreshth Srivastava <shreshth.srivastava@intel.com>
To: jgross@suse.com, linux-kernel@vger.kernel.org, x86@kernel.org,
linux-perf-users@vger.kernel.org, linux-hyperv@vger.kernel.org,
kvm@vger.kernel.org, linux-coco@lists.linux.dev
Cc: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, bp@alien8.de,
dave.hansen@linux.intel.com, decui@microsoft.com,
haiyangz@microsoft.com, hpa@zytor.com, irogers@google.com,
james.clark@linaro.org, jolsa@kernel.org, kas@kernel.org,
kys@microsoft.com, longli@microsoft.com, mark.rutland@arm.com,
mhklinux@outlook.com, mingo@redhat.com, namhyung@kernel.org,
pbonzini@redhat.com, peterz@infradead.org,
rick.p.edgecombe@intel.com, seanjc@google.com, tglx@kernel.org,
wei.liu@kernel.org, shreshth.srivastava@intel.com
Subject: Re: [PATCH v3 13/13] x86/msr: Simplify some rdmsrq() use cases
Date: Fri, 11 Sep 2026 17:33:10 -0400 [thread overview]
Message-ID: <20260911213310.381839-1-shreshth.srivastava@intel.com> (raw)
In-Reply-To: <20260821105709.1671132-1-jgross@suse.com>
Hi Juergen,
I'm working on a v3 of Dave's "x86/msr: Consolidate native/paravirt MSR
functions" series on top of yours, so I tried testing this patch.
While I'm here: you mentioned you'd send a V3 after rc1 if conflicts
turned up. Is that still the plan? I wasn't sure whether to base on v2
plus the respins of 4 and 13, or wait.
Most of the code this touches can't run on my box, so I compared compiled
output instead. Built patches 1-12, then 1-13, with the same .config and
compiler, and diffed "objdump -d" output for every .o in both trees. All
9396 objects came out identical. The 1-13 kernel boots fine under KVM.
Only tried the one config: x86_64, gcc 11.5.0,
CPU_SUP_{INTEL,AMD,ZHAOXIN}=y, HYPERV=y, KVM_INTEL=y, KVM_INTEL_TDX=y.
Tested-by: Shreshth Srivastava <shreshth.srivastava@intel.com>
next prev parent reply other threads:[~2026-09-11 21:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:23 [PATCH v2 00/13] x86/msr: Drop 32-bit MSR interfaces Juergen Gross
2026-08-19 10:23 ` [PATCH v2 12/13] treewide: convert rdmsrq() from a macro to an inline function Juergen Gross
2026-08-19 10:44 ` sashiko-bot
2026-08-20 6:06 ` Damien Le Moal
2026-08-21 4:13 ` Michael Kelley
2026-08-19 10:23 ` [PATCH v2 13/13] x86/msr: Simplify some rdmsrq() use cases Juergen Gross
2026-08-19 10:41 ` sashiko-bot
2026-08-19 15:28 ` Sean Christopherson
2026-08-19 15:31 ` Jürgen Groß
2026-08-21 4:13 ` Michael Kelley
2026-08-21 10:57 ` [PATCH v3 " Juergen Gross
2026-09-11 21:33 ` Shreshth Srivastava [this message]
2026-09-12 6:50 ` Jürgen Groß
2026-08-19 14:40 ` [PATCH v2 00/13] x86/msr: Drop 32-bit MSR interfaces Dave Hansen
2026-08-19 15:21 ` Jürgen Groß
2026-08-19 15:33 ` Sean Christopherson
2026-08-20 5:27 ` Jürgen Groß
-- strict thread matches above, loose matches on Subject: below --
2026-09-11 7:45 [PATCH v3 " Juergen Gross
2026-09-11 7:45 ` [PATCH v3 13/13] x86/msr: Simplify some rdmsrq() use cases Juergen Gross
2026-09-11 7:56 ` sashiko-bot
2026-09-11 13:20 ` 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=20260911213310.381839-1-shreshth.srivastava@intel.com \
--to=shreshth.srivastava@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jgross@suse.com \
--cc=jolsa@kernel.org \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kys@microsoft.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mark.rutland@arm.com \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=wei.liu@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox