public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "mitchell.augustin via groups.io" <mitchell.augustin=canonical.com@groups.io>
To: mitchell.augustin@canonical.com, devel@edk2.groups.io
Subject: Re: [edk2-devel] [BUG] Extremely slow boot times with CPU and GPU passthrough and host phys-bits > 40
Date: Fri, 14 Feb 2025 15:59:04 -0800	[thread overview]
Message-ID: <23568.1739577544707558908@groups.io> (raw)
In-Reply-To: <20236.1733324181278436066@groups.io>

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

Hello!

There has been some great progress on this in the kernel over the past couple months, so I wanted to provide an update on the resolution here for any past/future readers of this thread.

There is now a patch series ( https://lore.kernel.org/all/20250205231728.2527186-1-alex.williamson@redhat.com/ ) under review to fix the root cause of this issue in the kernel. In my tests, when this series is applied on both the host and guest kernels of an affected system, it eliminates the extra boot time entirely.

The complete solution in the series above relies on huge pfnmap support, but older pre-huge-pfnmap kernels will still be able to benefit from this patch set ( https://lore.kernel.org/all/20250111210652.402845-1-alex.williamson@redhat.com/ ) , which eliminates about half of the excess boot time by removing many redundant decode disable/enable toggles during initialization.

Thanks,
Mitchell Augustin


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121123): https://edk2.groups.io/g/devel/message/121123
Mute This Topic: https://groups.io/mt/109651206/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 1921 bytes --]

  reply	other threads:[~2025-02-14 23:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 16:46 [edk2-devel] [BUG] Extremely slow boot times with CPU and GPU passthrough and host phys-bits > 40 mitchell.augustin via groups.io
2024-11-18 21:14 ` xpahos via groups.io
2024-11-19 22:25   ` mitchell.augustin via groups.io
2024-11-20  9:35     ` xpahos via groups.io
2024-11-20 11:26     ` Gerd Hoffmann via groups.io
2024-11-20 15:20       ` mitchell.augustin via groups.io
2024-11-20 20:00         ` mitchell.augustin via groups.io
2024-11-21 12:32         ` Gerd Hoffmann via groups.io
2024-11-22  0:23           ` mitchell.augustin via groups.io
2024-11-22 10:35             ` Gerd Hoffmann via groups.io
2024-11-22 17:38               ` Brian J. Johnson via groups.io
2024-11-22 22:32               ` mitchell.augustin via groups.io
2024-11-24  2:05                 ` mitchell.augustin via groups.io
2024-11-25 11:47                   ` Gerd Hoffmann via groups.io
2024-11-25 19:58                     ` mitchell.augustin via groups.io
2024-11-26  8:09                       ` Gerd Hoffmann via groups.io
2024-11-26 22:27                         ` mitchell.augustin via groups.io
2024-12-04 14:56                           ` mitchell.augustin via groups.io
2025-02-14 23:59                             ` mitchell.augustin via groups.io [this message]
2024-11-25 11:18                 ` Gerd Hoffmann via groups.io
2024-11-18 21:32 ` Ard Biesheuvel via groups.io

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=23568.1739577544707558908@groups.io \
    --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