From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Alexey Kardashevskiy <aik@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest
Date: Thu, 28 Sep 2023 11:32:51 +0200 [thread overview]
Message-ID: <ZRVIQwkYO5XYhRtD@gmail.com> (raw)
In-Reply-To: <20230927112259.GAZRQQk78aJN85ULm1@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Wed, Sep 27, 2023 at 11:48:33AM +0200, Ingo Molnar wrote:
> > Not sure how this was supposed to work - there's no 'ghcb' passed in to
> > snp_cpuid_postprocess(). Does this patch have a dependency perhaps, that
> > I missed?
>
> Yes, it is explained above the diffstat. I'll take care of it when I get back.
Erm, yes indeed - I checked the first dependency which had the wrong SHA1
listed and which dependency is already upstream as 8dbe33956d96, but I missed
the second dependency:
> > > plus:
> > > https://lore.kernel.org/lkml/a5856fa1ebe3879de91a8f6298b6bbd901c61881.1690578565.git.thomas.lendacky@amd.com/
Alexey, for the v3 submission, instead of sending a standalone patch
that relies on a yet unmerged patch that was last submitted about two
months ago, please send a full series of patches that is self-consistent.
Ie. it should look something like this:
[PATCH 0/2] x86: Misc SEV-SNP fixes
[PATCH 1/2] x86/sev: Fix SNP CPUID requests to the hypervisor
[PATCH 2/2] x86/compressed/64: Reduce #VC nesting for intercepted CPUID for SEV-SNP guest
( You can add your SOB to Tom's first patch, to signal that you
tested it and are forwarding it, and that your fix relies on that fix. )
Thanks,
Ingo
next prev parent reply other threads:[~2023-09-28 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 4:05 [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest Alexey Kardashevskiy
2023-09-26 18:28 ` Tom Lendacky
2023-09-27 8:50 ` [tip: x86/mm] x86/sev: Reduce #VC nesting for intercepted CPUID for SEV-SNP guest, to fix nesting crash tip-bot2 for Alexey Kardashevskiy
2023-09-27 9:48 ` [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest Ingo Molnar
2023-09-27 11:22 ` Borislav Petkov
2023-09-28 9:32 ` Ingo Molnar [this message]
2023-09-30 7:17 ` Borislav Petkov
2023-10-01 9:40 ` Alexey Kardashevskiy
2023-10-01 9:53 ` Borislav Petkov
2023-10-01 12:17 ` Ingo Molnar
2023-10-01 12:31 ` Ingo Molnar
2023-10-03 1:45 ` Alexey Kardashevskiy
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=ZRVIQwkYO5XYhRtD@gmail.com \
--to=mingo@kernel.org \
--cc=aik@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=thomas.lendacky@amd.com \
--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 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.