mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: bp@kernel.org, thomas.lendacky@amd.com,
	linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	michael.roth@amd.com, x86@kernel.org
Subject: Re: [PATCH] x86/sev: Apply RMP table fixups for kexec.
Date: Tue, 2 Apr 2024 13:41:05 -0500	[thread overview]
Message-ID: <37321af9-aee4-4ba6-81ac-0df4cef38644@amd.com> (raw)
In-Reply-To: <20240402174540.GAZgxERNxsRJUCb1yp@fat_crate.local>


On 4/2/2024 12:45 PM, Borislav Petkov wrote:

> On Tue, Apr 02, 2024 at 12:11:03PM -0500, Kalra, Ashish wrote:
>>> And if you mean the reservation in the kernel page tables (directmap)
>>> then that will not help as kexec uses it's own identity mapped page
>>> tables.
> So how hard would it be to *always* reserve the chunk of memory at the
> 2M boundary where the RMP table starts and up to the 2M boundary where
> the RMP  table ends?
>
> In *every* kernel.

But, that's what the e820 table fixup is doing, it is reserving the 
chunk of memory at the 2M boundary where the RMP table starts and ends 
in the e820. Kexec is referring to the e820 table(s) for placing it's 
segments in memory for the kexec boot.

Thanks, Ashish

>
> By default.
>
> Thx.
>

  reply	other threads:[~2024-04-02 18:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 18:47 Ashish Kalra
2024-03-13 10:58 ` Aithal, Srikanth
2024-04-02 14:45 ` bp
2024-04-02 15:54   ` Tom Lendacky
2024-04-02 16:34     ` bp
2024-04-02 17:06       ` Kalra, Ashish
2024-04-02 17:11         ` Kalra, Ashish
2024-04-02 17:45           ` Borislav Petkov
2024-04-02 18:41             ` Kalra, Ashish [this message]
2024-04-02 18:50               ` Borislav Petkov
2024-04-02 19:33                 ` Kalra, Ashish
2024-04-02 20:21                   ` Borislav Petkov
2024-04-02 21:00                     ` Kalra, Ashish
2024-04-02 21:17                       ` Kalra, Ashish
2024-04-02 21:20                       ` Borislav Petkov
2024-04-02 21:31                         ` Kalra, Ashish
2024-04-02 21:40                           ` Borislav Petkov
2024-04-02 22:09 ` Tom Lendacky
2024-04-02 22:31   ` Kalra, Ashish
2024-04-02 22:42     ` Michael Roth
2024-04-03 21:08       ` Kalra, Ashish
2024-04-04  8:17         ` Jeremi Piotrowski
2024-04-04 18:07           ` Kalra, Ashish

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=37321af9-aee4-4ba6-81ac-0df4cef38644@amd.com \
    --to=ashish.kalra@amd.com \
    --cc=bp@alien8.de \
    --cc=bp@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=michael.roth@amd.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 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®