From: Lukas Wunner <lukas@wunner.de>
To: Aditya Garg <gargaditya08@live.com>
Cc: Lleyton Gray <lleyton@fyralabs.com>,
Ard Biesheuvel <ardb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>
Subject: Re: [PATCH] x86/efistub: Add options for forcing Apple set_os protocol
Date: Mon, 10 Feb 2025 21:09:09 +0100 [thread overview]
Message-ID: <Z6pc5SYaMhOfXeDz@wunner.de> (raw)
In-Reply-To: <PN3PR01MB7728B4C94846673A5FFACE29B80B2@PN3PR01MB7728.INDPRD01.PROD.OUTLOOK.COM>
On Wed, Jan 01, 2025 at 11:39:13AM +0000, Aditya Garg wrote:
> We have had issues with other people unable to use their eGPU if their
> Mac doesn't have the apple set os quirk. We probably could do dual VGA
> checks suggested by Lukas, but will it work with GPU hotplug?
About hotplug: There is a tiny time window when the EFI stub runs
during which an eGPU may be hotplugged and incorrectly not be
detected. I.e. the quirk is not applied. I don't think this can
be fixed.
If an eGPU is hotplugged while EFI boot services are still running,
Apple's EFI Thunderbolt driver will set up a tunnel to the device
and it will then be visible to the kernel's efi stub. E.g. if you
hold down the Option key during boot and attach an eGPU, then
select the operating system to boot, the eGPU should correctly be
seen by the efi stub and the quirk is applied.
However hotplugging an eGPU at exactly the moment when the efi stub
runs results in a race between the efi stub doing all the initialization
and exiting boot services on the one hand, and the EFI Thunderbolt
driver bringing up the eGPU on the other hand.
But IMO this is "good enough".
Thanks,
Lukas
next prev parent reply other threads:[~2025-02-10 20:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 20:21 [PATCH] x86/efistub: Add options for forcing Apple set_os protocol Lleyton Gray
2024-12-29 9:59 ` Lukas Wunner
2024-12-29 10:08 ` Ard Biesheuvel
2024-12-29 10:38 ` Lukas Wunner
2024-12-29 18:22 ` Ard Biesheuvel
2024-12-30 3:09 ` Lleyton Gray
2025-02-10 19:25 ` Lukas Wunner
[not found] ` <PN3PR01MB7728B4C94846673A5FFACE29B80B2@PN3PR01MB7728.INDPRD01.PROD.OUTLOOK.COM>
2025-02-10 19:58 ` Lukas Wunner
2025-02-11 16:05 ` Aditya Garg
2025-02-13 4:56 ` Lukas Wunner
2025-02-10 20:09 ` Lukas Wunner [this message]
2025-02-11 5:45 ` Aditya Garg
2025-02-09 16:13 ` Aditya Garg
2025-02-10 10:40 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2025-02-10 10:51 Aditya Garg
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=Z6pc5SYaMhOfXeDz@wunner.de \
--to=lukas@wunner.de \
--cc=ardb@kernel.org \
--cc=gargaditya08@live.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lleyton@fyralabs.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