From: "Paluri, PavanKumar" <papaluri@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"VanTassell, Eric" <Eric.VanTassell@amd.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"Kalra, Ashish" <Ashish.Kalra@amd.com>,
"Roth, Michael" <Michael.Roth@amd.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paluri, PavanKumar (Pavan Kumar)" <PavanKumar.Paluri@amd.com>
Subject: Re: [PATCH 1/2] x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm
Date: Thu, 29 Aug 2024 10:53:17 -0500 [thread overview]
Message-ID: <9c632a10-9b68-c144-5477-197bf693651b@amd.com> (raw)
In-Reply-To: <20240829154156.GHZtCWxP7mkn7aVyWm@fat_crate.local>
On 8/29/2024 10:41 AM, Borislav Petkov wrote:
> On Thu, Aug 29, 2024 at 10:29:16AM -0500, Paluri, PavanKumar wrote:
>> So here's the updated diff (for patch #1) that is compile-tested:
>
> Make sure you build
>
> "allnoconfig" "defconfig" "allmodconfig" "allyesconfig"
>
> builds, for both 32-bit and 64-bit on each patch before you resend.
>
Sure, will build with all the above configurations and send v2.
> Thx.
>
Thanks,
Pavan
next prev parent reply other threads:[~2024-08-29 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 20:56 [PATCH 0/2] "nosnp" sev command line support Pavan Kumar Paluri
2024-08-01 20:56 ` [PATCH 1/2] x86, KVM:SVM: Move sev specific parsing into arch/x86/virt/svm Pavan Kumar Paluri
2024-08-02 14:18 ` Tom Lendacky
2024-08-29 13:24 ` Borislav Petkov
2024-08-29 14:22 ` Borislav Petkov
2024-08-29 15:29 ` Paluri, PavanKumar
2024-08-29 15:41 ` Borislav Petkov
2024-08-29 15:53 ` Paluri, PavanKumar [this message]
2024-08-01 20:56 ` [PATCH 2/2] x86 KVM:SVM: Provide "nosnp" boot option for sev kernel command line Pavan Kumar Paluri
2024-08-02 14:19 ` Tom Lendacky
2024-08-01 20:58 ` [PATCH 0/2] "nosnp" sev command line support Matthew Wilcox
2024-08-01 22:23 ` Paluri, PavanKumar
2024-08-01 22:39 ` Matthew Wilcox
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=9c632a10-9b68-c144-5477-197bf693651b@amd.com \
--to=papaluri@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=Eric.VanTassell@amd.com \
--cc=Michael.Roth@amd.com \
--cc=PavanKumar.Paluri@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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®