All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	 Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Borislav Petkov <bp@suse.de>, Andy Lutomirski <luto@kernel.org>,
	 Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>,
	 "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
	Thomas Gleixner <tglx@kernel.org>,
	 Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	 linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH v3 5/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls
Date: Fri, 10 Jul 2026 06:47:57 -0700	[thread overview]
Message-ID: <alD3ZFgfgMj0_qoT@gmail.com> (raw)
In-Reply-To: <alDW8vjjU_f7dkIK@e129823.arm.com>

On Fri, Jul 10, 2026 at 12:26:42PM +0100, Yeoreum Yun wrote:
> > On Fri, Jul 10, 2026 at 11:41:09AM +0100, Yeoreum Yun wrote:
> > > > Hello Yeoreum,
> > > > 
> > > > On Thu, Jul 09, 2026 at 07:56:18AM +0100, Yeoreum Yun wrote:
> > > > > 
> > > > > One of my concern is for the UpdateCapsule runtime service.
> > > > > It might have a case where takes more then 2 mins and there's one
> > > > > RFC to support a runtime capsule update for arm platform [1].
> > > > 
> > > > I'm not familiar with UpdateCapsule. Are you suggesting that a 2-minute
> > > > wait for an EFI call should be acceptable (?!)
> > > > 
> > > > Wouldn't that trigger stalls and hung-task/wq warnings throughout the
> > > > kernel?
> > > 
> > > Might for default config timeout for hung-task. However at least
> > > its timeout configurable.
> > > 
> > > TBH, normally it wouldn't task more than 2 mins.
> > > But for a in case of *slow firmware*, would be good to make
> > > runtime-service timeout configurable at least?
> > 
> > OK, that is fair request.
> > 
> > I would suggest we do an additional patch with this change, if Ard is
> > positive on the idea.
> > 
> > Yeoreum, would you like to do it, or should I do it?
> 
> It's up to you. I don't care who will do this :)
> But if you have no bandwidth, I'll take once your patch is merged
> and Ard agrees for this.

Sounds good. Let's wait for Ard's feedback on the additional patches
[1], and we can decide how to proceed from there.

Link: https://lore.kernel.org/all/alDDv3XGXVdd1mri@gmail.com/ [1]

  reply	other threads:[~2026-07-10 13:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 12:09 [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-06-16 12:09 ` [PATCH v3 1/7] efi: fix stale reference to efi_recover_from_page_fault() Breno Leitao
2026-06-16 12:09 ` [PATCH v3 2/7] efi/runtime-wrappers: factor out efi_rts_park_worker() Breno Leitao
2026-06-16 12:09 ` [PATCH v3 3/7] efi/runtime-wrappers: handle queue_work() failure with goto exit Breno Leitao
2026-06-16 12:09 ` [PATCH v3 4/7] efi/runtime-wrappers: check EFI_RUNTIME_SERVICES before using efi_rts_work Breno Leitao
2026-06-16 12:09 ` [PATCH v3 5/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-07-09  6:56   ` Yeoreum Yun
2026-07-10 10:30     ` Breno Leitao
2026-07-10 10:41       ` Yeoreum Yun
2026-07-10 11:14         ` Breno Leitao
2026-07-10 11:26           ` Yeoreum Yun
2026-07-10 13:47             ` Breno Leitao [this message]
2026-07-12 16:25               ` Ard Biesheuvel
2026-07-13 10:03                 ` Breno Leitao
2026-06-16 12:09 ` [PATCH v3 6/7] efi/runtime-wrappers: honour EFI_RUNTIME_SERVICES in the non-blocking paths Breno Leitao
2026-06-16 12:09 ` [PATCH v3 7/7] efi/runtime-wrappers: retire the worker if a wedged call ever returns Breno Leitao
2026-07-01 12:28 ` [PATCH v3 0/7] efi/runtime-wrappers: bound the wait for EFI runtime service calls Breno Leitao
2026-07-09  5:02   ` Ard Biesheuvel
2026-07-10 10:06     ` Breno Leitao

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=alD3ZFgfgMj0_qoT@gmail.com \
    --to=leitao@debian.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gpiccoli@igalia.com \
    --cc=hpa@zytor.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kees@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=yeoreum.yun@arm.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 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.