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>,
	Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied:  [PATCH v2 qemu] add two more stable patches
Date: Tue, 19 Jul 2022 17:22:56 +0200	[thread overview]
Message-ID: <ce2aa59d-b655-1079-9d6a-ece61b6a0050@proxmox.com> (raw)
In-Reply-To: <20220719081931.63413-1-f.ebner@proxmox.com>

Am 19/07/2022 um 10:19 schrieb Fabian Ebner:
> For the io_uring patch, it's not very clear which configurations can
> trigger it, but it should be rather uncommon. See qemu commit
> be6a166fde652589761cf70471bcde623e9bd72a for a bit more information.
> 
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> 
> Changes from v1:
>     * Cherry-pick io_uring patch instead of taking it from mail (was
>       applied upstream in the meantime).
>     * Include patch for e1000 issue.
> 
>  ...20-io_uring-fix-short-read-slow-path.patch | 49 +++++++++++
>  ...criptor-status-in-a-separate-operati.patch | 82 +++++++++++++++++++
>  debian/patches/series                         |  2 +
>  3 files changed, 133 insertions(+)
>  create mode 100644 debian/patches/extra/0020-io_uring-fix-short-read-slow-path.patch
>  create mode 100644 debian/patches/extra/0021-e1000-set-RX-descriptor-status-in-a-separate-operati.patch
> 
>

applied, thanks!




      reply	other threads:[~2022-07-19 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  8:19 [pve-devel] " Fabian Ebner
2022-07-19 15:22 ` 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=ce2aa59d-b655-1079-9d6a-ece61b6a0050@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