From: Aditya Garg <gargaditya08@live.com>
To: Lukas Wunner <lukas@wunner.de>
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: Tue, 11 Feb 2025 05:45:30 +0000 [thread overview]
Message-ID: <PN0PR01MB960815D7115B2DE62E27DCC4B8FD2@PN0PR01MB9608.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Z6pc5SYaMhOfXeDz@wunner.de>
> On 11 Feb 2025, at 1:39 AM, Lukas Wunner <lukas@wunner.de> wrote:
>
> 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".
Something is better than nothing.
I'll test your patch, and imo restricting it to Apple devices should be a good idea.
>
> Thanks,
>
> Lukas
next prev parent reply other threads:[~2025-02-11 5:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 20:21 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
2025-02-11 5:45 ` Aditya Garg [this message]
2025-02-09 16:13 ` Aditya Garg
2025-02-10 10:40 ` Ard Biesheuvel
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=PN0PR01MB960815D7115B2DE62E27DCC4B8FD2@PN0PR01MB9608.INDPRD01.PROD.OUTLOOK.COM \
--to=gargaditya08@live.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lleyton@fyralabs.com \
--cc=lukas@wunner.de \
/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
all inboxes | Powered by JetHome®