From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Pawel Polawski <ppolawsk@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH v2 0/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL
Date: Tue, 9 May 2023 14:23:31 +0000 [thread overview]
Message-ID: <0102018800e55c15-06451e86-006c-45d0-91ee-106189471d0b-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <bb6edf7b-a0cf-ed7e-e7d2-d9afb2360ba9@redhat.com>
On 09/05/2023 14:31, Laszlo Ersek wrote:
> On 5/9/23 14:09, Michael Brown wrote:
>> At TPL_HIGH_LEVEL, CPU interrupts are disabled (as per the UEFI
>> specification) and so we should never encounter a situation in which
>> an interrupt occurs at TPL_HIGH_LEVEL. The specification also
>> restricts usage of TPL_HIGH_LEVEL to the firmware itself.
>>
>> However, nothing actually prevents a UEFI application from calling
>> gBS->RaiseTPL(TPL_HIGH_LEVEL) and then violating the invariant by
>> enabling interrupts via the STI or equivalent instruction. Some
>> versions of the Microsoft Windows bootloader are known to do this.
>>
>> NestedInterruptTplLib maintains the invariant that interrupts are
>> disabled at TPL_HIGH_LEVEL (even when performing the dark art of
>> deliberately manipulating the stack so that IRET will return with
>> interrupts still disabled), but does not itself rely on external code
>> maintaining this invariant.
>>
>> Relax the assertion that the interrupted TPL is below TPL_HIGH_LEVEL
>> to an error message, to allow UEFI applications such as these versions
>> of the Microsoft Windows bootloader to continue to function.
>>
>> Ref: https://bugzilla.redhat.com/show_bug.cgi?id=2189136
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Gerd Hoffmann <kraxel@redhat.com>
>> Cc: Oliver Steffen <osteffen@redhat.com>
>> Cc: Pawel Polawski <ppolawsk@redhat.com>
>> Cc: Jiewen Yao <jiewen.yao@intel.com>
>> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>>
>> Michael Brown (2):
>> OvmfPkg: Clarify invariants for NestedInterruptTplLib
>> OvmfPkg: Relax assertion that interrupts do not occur at
>> TPL_HIGH_LEVEL
>>
>> OvmfPkg/Library/NestedInterruptTplLib/Tpl.c | 31 +++++++++++++++++----
>> 1 file changed, 26 insertions(+), 5 deletions(-)
>>
>
> series
> Acked-by: Laszlo Ersek <lersek@redhat.com>
Thank you!
Gerd: are you happy for your Reviewed-by to stand, since the only
changes since v1 were to comment wording? (My apologies for forgetting
to include a v2 description in the cover letter.)
Thanks,
Michael
next prev parent reply other threads:[~2023-05-09 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175D7813A02A6FCA.31428@groups.io>
2023-05-09 12:09 ` [PATCH v2 0/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL Michael Brown
2023-05-09 13:31 ` Laszlo Ersek
2023-05-09 14:23 ` Michael Brown [this message]
2023-05-09 21:49 ` [edk2-devel] " Ard Biesheuvel
2023-05-10 6:12 ` Ard Biesheuvel
[not found] ` <20230509120909.3970177-1-mcb30@ipxe.org>
2023-05-09 12:09 ` [PATCH v2 1/2] OvmfPkg: Clarify invariants for NestedInterruptTplLib Michael Brown
2023-05-09 12:09 ` [PATCH v2 2/2] OvmfPkg: Relax assertion that interrupts do not occur at TPL_HIGH_LEVEL Michael Brown
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-list 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=0102018800e55c15-06451e86-006c-45d0-91ee-106189471d0b-000000@eu-west-1.amazonses.com \
--to=devel@edk2.groups.io \
/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