Linux-EFI Archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb+git@google.com>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] EFI fix for v6.9 (#1)
Date: Fri,  3 May 2024 13:03:03 +0200	[thread overview]
Message-ID: <20240503110302.2339230-2-ardb+git@google.com> (raw)

From: Ard Biesheuvel <ardb@kernel.org>

Hello Linus,

Please pull the EFI fix below - it works around a shortcoming in the memory
acceptation API, which may apparently hog the CPU for long enough to trigger
the softlockup watchdog. Note that this only affects confidential VMs running
under the Intel TDX hypervisor, which is why I accepted this for now, but this
should obviously be fixed properly in the future.


The following changes since commit 0bbac3facb5d6cc0171c45c9873a2dc96bea9680:

  Linux 6.9-rc4 (2024-04-14 13:38:39 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v6.9-1

for you to fetch changes up to 1c5a1627f48105cbab81d25ec2f72232bfaa8185:

  efi/unaccepted: touch soft lockup during memory accept (2024-04-24 19:11:34 +0200)

----------------------------------------------------------------
EFI fix for v6.9 (#1)

- Avoid triggering the softlockup watchdog when accepting large chunks
  of memory from the hypervisor

----------------------------------------------------------------
Chen Yu (1):
      efi/unaccepted: touch soft lockup during memory accept

 drivers/firmware/efi/unaccepted_memory.c | 4 ++++
 1 file changed, 4 insertions(+)

             reply	other threads:[~2024-05-03 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 11:03 Ard Biesheuvel [this message]
2024-05-03 21:44 ` [GIT PULL] EFI fix for v6.9 (#1) pr-tracker-bot

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=20240503110302.2339230-2-ardb+git@google.com \
    --to=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).