public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-qemu 1/2] enable io-uring support in QEMU builds
Date: Mon,  7 Jun 2021 13:48:49 +0200	[thread overview]
Message-ID: <20210607114850.964814-2-s.reiter@proxmox.com> (raw)
In-Reply-To: <20210607114850.964814-1-s.reiter@proxmox.com>

Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
---

Oh if only all QEMU changes were this simple...

 debian/control | 1 +
 debian/rules   | 1 +
 2 files changed, 2 insertions(+)

diff --git a/debian/control b/debian/control
index 38c45ce..4da3409 100644
--- a/debian/control
+++ b/debian/control
@@ -27,6 +27,7 @@ Build-Depends: autotools-dev,
                libspice-protocol-dev (>= 0.12.14~),
                libspice-server-dev (>= 0.14.0~),
                libsystemd-dev,
+               liburing-dev,
                libusb-1.0-0-dev (>= 1.0.17-1),
                libusbredirparser-dev (>= 0.6-2),
                meson,
diff --git a/debian/rules b/debian/rules
index 1f623d8..0417703 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,6 +69,7 @@ ${BUILDDIR}/config.status: configure
 	--enable-libiscsi \
 	--enable-libusb \
 	--enable-linux-aio \
+	--enable-linux-io-uring \
 	--enable-numa \
 	--enable-rbd \
 	--enable-seccomp \
-- 
2.30.2





  reply	other threads:[~2021-06-07 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 11:48 [pve-devel] [PATCH 0/2] Enable io-uring support in QEMU Stefan Reiter
2021-06-07 11:48 ` Stefan Reiter [this message]
2021-06-21  7:57   ` [pve-devel] applied: [PATCH pve-qemu 1/2] enable io-uring support in QEMU builds Thomas Lamprecht
2021-06-07 11:48 ` [pve-devel] [PATCH qemu-server 2/2] enable io-uring support Stefan Reiter
2021-06-21  8:00   ` 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=20210607114850.964814-2-s.reiter@proxmox.com \
    --to=s.reiter@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