From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, patrick.henz@hpe.com
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/XhciDxe: Use Performance Timer for XHCI Timeouts
Date: Thu, 6 Jul 2023 13:02:07 +0000 [thread overview]
Message-ID: <010201892b4badcf-078f8af5-8d8c-4e1e-903b-60c005a5b8a8-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <dba8986692c5622e4426fd5f0802052cbff81919.1688139532.git.patrick.henz@hpe.com>
On 05/07/2023 21:15, Henz, Patrick wrote:
> REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2948
>
> XhciDxe uses the timer functionality provided by the
> boot services table to detect timeout conditions. This
> breaks the driver's ExitBootServices call back, as
> CoreExitBootServices halts the timer before signaling
> the ExitBootServices event. If the host controller
> fails to halt in the call back, the timeout condition
> will never occur and the boot gets stuck in an indefinite
> spin loop. Use the free running timer provided by
> TimerLib to calculate timeouts, avoiding the potential
> hang.
Two points:
1. The XhcGetElapsedTime() function feels like a generally reusable
abstraction that should exist within TimerLib, rather than being
open-coded within XhciDxe.
2. Is the performance counter guaranteed to exist and work as expected
on all platforms and CPU architectures? (For example: what if the CPU
does not support a constant TSC?)
Thanks,
Michael
next prev parent reply other threads:[~2023-07-06 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 20:15 [PATCH] MdeModulePkg/XhciDxe: Use Performance Timer for XHCI Timeouts Henz, Patrick
2023-07-06 13:02 ` Michael Brown [this message]
2023-07-06 14:19 ` [edk2-devel] " Henz, Patrick
2023-07-06 15:47 ` Michael Brown
2023-07-06 18:01 ` Michael D Kinney
2023-07-31 2:57 ` Wu, Hao A
2023-08-10 22:44 ` Henz, Patrick
2023-08-11 1:43 ` Wu, Hao A
2023-10-30 20:36 ` Henz, Patrick
2023-10-31 1:41 ` Wu, Hao A
2023-10-31 12:14 ` Laszlo Ersek
2023-10-31 12:16 ` Laszlo Ersek
2023-10-31 13:38 ` Henz, Patrick
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=010201892b4badcf-078f8af5-8d8c-4e1e-903b-60c005a5b8a8-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