public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH qemu] revert hpet changes to fix performance regression
Date: Wed, 26 Mar 2025 10:10:05 +0100	[thread overview]
Message-ID: <b9668b56-c98f-4eaa-9587-169b2f926e7c@proxmox.com> (raw)
In-Reply-To: <20250319163930.294610-1-f.ebner@proxmox.com>

Am 19.03.25 um 17:39 schrieb Fiona Ebner:
> As reported in the community forum [0][1], QEMU processes for Linux
> guests would consume more CPU on the host after an update to QEMU 9.2.
> The issue was reproduced and bisecting pointed to QEMU commit
> f0ccf77078 ("hpet: fix and cleanup persistence of interrupt status").
> 
> Some quick experimentation suggests that in particular the last part
>  is responsible for the issue:
>> - the timer must be kept running even if not enabled, in
>>   order to set the ISR flag, so writes to HPET_TN_CFG must
>>   not call hpet_del_timer()
> 
> Users confirmed that setting the hpet=off machine flag works around
> the issue[0]. For Windows (7 or later) guests, the flag is already
> disabled, because of issues in the past [2].
> 
> Upstream suggested reverting the relevant patches for now [3], because
> other issues were reported too. All except commit 5895879aca ("hpet:
> remove unnecessary variable "index"") are actually dependent on each
> other for cleanly reverting f0ccf77078, and while not strictly
> required, that one was reverted too for completeness.
> 
> [0]: https://forum.proxmox.com/threads/163694/
> [1]: https://forum.proxmox.com/threads/161849/post-756793
> [2]: https://lists.proxmox.com/pipermail/pve-devel/2012-December/004958.html
> [3]: https://lore.kernel.org/qemu-devel/CABgObfaKJ5NFVKmYLFmu4C0iZZLJJtcWksLCzyA0tBoz0koZ4A@mail.gmail.com/
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  ...void-timer-storms-on-periodic-timers.patch |  50 ++++
>  ...e-full-64-bit-target-value-of-the-co.patch | 203 +++++++++++++
>  ...-hpet-accept-64-bit-reads-and-writes.patch | 281 ++++++++++++++++++
>  ...e-read-only-bits-directly-in-new_val.patch |  64 ++++
>  ...et-remove-unnecessary-variable-index.patch |  68 +++++
>  ...re-high-bits-of-comparator-in-32-bit.patch |  40 +++
>  ...and-cleanup-persistence-of-interrupt.patch | 120 ++++++++
>  debian/patches/series                         |   7 +
>  8 files changed, 833 insertions(+)
>  create mode 100644 debian/patches/pve/0051-Revert-hpet-avoid-timer-storms-on-periodic-timers.patch
>  create mode 100644 debian/patches/pve/0052-Revert-hpet-store-full-64-bit-target-value-of-the-co.patch
>  create mode 100644 debian/patches/pve/0053-Revert-hpet-accept-64-bit-reads-and-writes.patch
>  create mode 100644 debian/patches/pve/0054-Revert-hpet-place-read-only-bits-directly-in-new_val.patch
>  create mode 100644 debian/patches/pve/0055-Revert-hpet-remove-unnecessary-variable-index.patch
>  create mode 100644 debian/patches/pve/0056-Revert-hpet-ignore-high-bits-of-comparator-in-32-bit.patch
>  create mode 100644 debian/patches/pve/0057-Revert-hpet-fix-and-cleanup-persistence-of-interrupt.patch
> 
>

applied, thanks!

nit: would have moved the patches in another folder, potentially a new
dedicated hpet one, as this isn't a pve downstream adaption/extension,
but no biggie.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      reply	other threads:[~2025-03-26  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 16:39 [pve-devel] " Fiona Ebner
2025-03-26  9:10 ` Thomas Lamprecht [this message]

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=b9668b56-c98f-4eaa-9587-169b2f926e7c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal