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 2/2] update reentrancy patches to version in upstream git
Date: Tue, 6 Jun 2023 18:03:22 +0200	[thread overview]
Message-ID: <39716a37-95cc-0351-bf1c-01be655a1546@proxmox.com> (raw)
In-Reply-To: <20230606085850.48577-2-f.ebner@proxmox.com>

Am 06/06/2023 um 10:58 schrieb Fiona Ebner:
> The previous version was picked from the mailing list and still had
> an object_dynamic_cast call in a hot path, which is avoided with the
> version that landed in git.
> 
> Also adds a few more exceptions for devices that need reentrancy.
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  ...-memory-prevent-dma-reentracy-issues.patch | 118 ----------------
>  ...s-Internal-cdbs-have-16-byte-length.patch} |   0
>  ...al-deadlock-when-draining-during-tr.patch} |   0
>  ...en-getting-cursor-without-a-console.patch} |   0
>  ...isabling-re-entrancy-checking-per-MR.patch |  38 -----
>  ...-memory-prevent-dma-reentracy-issues.patch | 130 ++++++++++++++++++
>  ...le-reentrancy-detection-for-script-R.patch |   8 +-
>  ...-disable-reentrancy-detection-for-io.patch |  37 +++++
>  ...sable-reentrancy-detection-for-iomem.patch |  35 +++++
>  ...le-reentrancy-detection-for-apic-msi.patch |  36 +++++
>  debian/patches/series                         |  12 +-
>  11 files changed, 252 insertions(+), 162 deletions(-)
>  delete mode 100644 debian/patches/extra/0002-memory-prevent-dma-reentracy-issues.patch
>  rename debian/patches/extra/{0003-scsi-megasas-Internal-cdbs-have-16-byte-length.patch => 0002-scsi-megasas-Internal-cdbs-have-16-byte-length.patch} (100%)
>  rename debian/patches/extra/{0004-ide-avoid-potential-deadlock-when-draining-during-tr.patch => 0003-ide-avoid-potential-deadlock-when-draining-during-tr.patch} (100%)
>  rename debian/patches/extra/{0007-ui-return-NULL-when-getting-cursor-without-a-console.patch => 0004-ui-return-NULL-when-getting-cursor-without-a-console.patch} (100%)
>  delete mode 100644 debian/patches/extra/0005-memory-Allow-disabling-re-entrancy-checking-per-MR.patch
>  create mode 100644 debian/patches/extra/0005-memory-prevent-dma-reentracy-issues.patch
>  create mode 100644 debian/patches/extra/0007-bcm2835_property-disable-reentrancy-detection-for-io.patch
>  create mode 100644 debian/patches/extra/0008-raven-disable-reentrancy-detection-for-iomem.patch
>  create mode 100644 debian/patches/extra/0009-apic-disable-reentrancy-detection-for-apic-msi.patch
> 
>

applied, thanks!




  reply	other threads:[~2023-06-06 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  8:58 [pve-devel] [PATCH qemu 1/2] update submodule and patches to QEMU 8.0.2 Fiona Ebner
2023-06-06  8:58 ` [pve-devel] [PATCH qemu 2/2] update reentrancy patches to version in upstream git Fiona Ebner
2023-06-06 16:03   ` Thomas Lamprecht [this message]
2023-06-06 16:03 ` [pve-devel] applied: [PATCH qemu 1/2] update submodule and patches to QEMU 8.0.2 Thomas Lamprecht

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=39716a37-95cc-0351-bf1c-01be655a1546@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