From: Borislav Petkov <bp@alien8.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-coco@lists.linux.dev, kvm@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Ard Biesheuvel <ardb@kernel.org>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:EXTENSIBLE FIRMWARE INTERFACE (EFI)"
<linux-efi@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] x86/sev: let sev_es_efi_map_ghcbs map the caa pages too
Date: Wed, 25 Jun 2025 14:40:16 +0200 [thread overview]
Message-ID: <20250625124016.GCaFvuMA9oApInTVyI@fat_crate.local> (raw)
In-Reply-To: <rite3te5udzekwbbujmga5kyyjjm5gfphhqoxlhtsncgckq6rm@7m7owl5jgubz>
On Wed, Jun 25, 2025 at 01:52:58PM +0200, Gerd Hoffmann wrote:
> The kernel allocates the caa page(s) only when running under svsm, see
> alloc_runtime_data(), so this is not correct. I think we either have to
> return to the original behavior of only doing something in case address
> is not NULL
Yes, we're doing something only when the address is not NULL.
Or maybe I'm missing what you're trying to tell me...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-06-25 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250602105050.1535272-1-kraxel@redhat.com>
2025-06-02 10:50 ` [PATCH v2 2/2] x86/sev: let sev_es_efi_map_ghcbs map the caa pages too Gerd Hoffmann
2025-06-24 13:01 ` Borislav Petkov
2025-06-25 11:52 ` Gerd Hoffmann
2025-06-25 12:40 ` Borislav Petkov [this message]
2025-06-25 13:21 ` Gerd Hoffmann
2025-06-25 14:29 ` Borislav Petkov
2025-06-26 7:43 ` Gerd Hoffmann
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=20250625124016.GCaFvuMA9oApInTVyI@fat_crate.local \
--to=bp@alien8.de \
--cc=ardb@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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