public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <andrew.jones@linux.dev>
To: Pavan Kumar Paluri <papaluri@amd.com>
Cc: kvm@vger.kernel.org, thomas.lendacky@amd.com, michael.roth@amd.com
Subject: Re: [kvm-unit-tests PATCH v4 0/2] UEFI Improvements
Date: Wed, 3 Apr 2024 13:27:06 +0200	[thread overview]
Message-ID: <20240403-e1c5baaf0963235f15bfaad2@orel> (raw)
In-Reply-To: <20240329131522.806983-1-papaluri@amd.com>

On Fri, Mar 29, 2024 at 08:15:20AM -0500, Pavan Kumar Paluri wrote:
> Patch-1: Introduces a fix for x86 arch which is ACPI-based to not get
> 	 into the path of fdt.
> 
> Patch-2: KUT UEFI-based guest may sometimes fail to exit boot services
> 	 due to a possible memory map update that might have taken place
> 	 between efi_get_memory_map() call and efi_exit_boot_services()
> 	call. As per UEFI specification (2.10), we need to try and keep
> 	updating the memory map as long as we get Invalid key failure.
> 
> =========
> Changelog
> =========
> v3 -> v4:
>     * Dropped patches 3 & 4 from the series as they are not relevant to 
>       UEFI improvements introduced in this patchset. This would aid in 
>       easier review and upstreaming.
>     * Addressed feedback (Andrew)
>     * Included R-b tag from Andrew Jones.
> 
> v2 -> v3:
>     * Included R-b tag from Andrew for Patch-1.
>     * Updated patch-2 to not leak memory map information during 
>       re-trials to efi_get_memory_map().
> 
> v1 -> v2:
>     * Incorporated feedback (Andrew, Mike, Tom)
>     * Updated patch-2 to keep trying to update memory map and calls to 
>       exit boot services as long as there is a failure.
>     * Split Page allocation and GHCB page attributes patch into two 
>       patches.
>  
> Pavan Kumar Paluri (2):
>   x86 EFI: Bypass call to fdt_check_header()
>   x86/efi: Retry call to efi exit boot services
> 
>  lib/efi.c | 39 +++++++++++++++++++++++++--------------
>  1 file changed, 25 insertions(+), 14 deletions(-)
> 
> -- 
> 2.34.1
>

Merged.

Thanks,
drew

      parent reply	other threads:[~2024-04-03 11:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 13:15 [kvm-unit-tests PATCH v4 0/2] UEFI Improvements Pavan Kumar Paluri
2024-03-29 13:15 ` [kvm-unit-tests PATCH v4 1/2] x86 EFI: Bypass call to fdt_check_header() Pavan Kumar Paluri
2024-03-29 13:15 ` [kvm-unit-tests PATCH v4 2/2] x86/efi: Retry call to efi exit boot services Pavan Kumar Paluri
2024-04-03 11:27 ` Andrew Jones [this message]

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=20240403-e1c5baaf0963235f15bfaad2@orel \
    --to=andrew.jones@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=papaluri@amd.com \
    --cc=thomas.lendacky@amd.com \
    /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