virtio-fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	virtio-fs@redhat.com, qemu-block@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Fam Zheng <fam@euphon.net>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Virtio-fs] [PULL 0/6] Block patches
Date: Thu,  9 Feb 2023 10:25:14 -0500	[thread overview]
Message-ID: <20230209152520.434183-1-stefanha@redhat.com> (raw)

The following changes since commit 417296c8d8588f782018d01a317f88957e9786d6:

  tests/qtest/netdev-socket: Raise connection timeout to 60 seconds (2023-02-09 11:23:53 +0000)

are available in the Git repository at:

  https://gitlab.com/stefanha/qemu.git tags/block-pull-request

for you to fetch changes up to acbc8aee5b09222dc6a5cb88306b67bcbe37e30b:

  iotests/detect-zeroes-registered-buf: add new test (2023-02-09 10:22:30 -0500)

----------------------------------------------------------------
Pull request

A few fixes that I've picked up.

----------------------------------------------------------------

Akihiko Odaki (1):
  vhost-user-fs: Back up vqs before cleaning up vhost_dev

Emanuele Giuseppe Esposito (1):
  virtio-blk: add missing AioContext lock

Stefan Hajnoczi (4):
  block: fix detect-zeroes= with BDRV_REQ_REGISTERED_BUF
  qemu-io: use BdrvRequestFlags instead of int
  qemu-io: add -r option to register I/O buffer
  iotests/detect-zeroes-registered-buf: add new test

 block/io.c                                    |   3 +
 hw/block/virtio-blk.c                         |   5 +
 hw/virtio/vhost-user-fs.c                     |   4 +-
 qemu-io-cmds.c                                | 215 +++++++++++-------
 .../tests/detect-zeroes-registered-buf        |  58 +++++
 .../tests/detect-zeroes-registered-buf.out    |   7 +
 6 files changed, 210 insertions(+), 82 deletions(-)
 create mode 100755 tests/qemu-iotests/tests/detect-zeroes-registered-buf
 create mode 100644 tests/qemu-iotests/tests/detect-zeroes-registered-buf.out

-- 
2.39.1


             reply	other threads:[~2023-02-09 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-09 15:25 Stefan Hajnoczi [this message]
2023-02-09 15:25 ` [Virtio-fs] [PULL 1/6] vhost-user-fs: Back up vqs before cleaning up vhost_dev Stefan Hajnoczi
2023-02-09 15:25 ` [Virtio-fs] [PULL 2/6] virtio-blk: add missing AioContext lock Stefan Hajnoczi
2023-02-09 15:25 ` [Virtio-fs] [PULL 3/6] block: fix detect-zeroes= with BDRV_REQ_REGISTERED_BUF Stefan Hajnoczi
2023-02-09 15:25 ` [Virtio-fs] [PULL 4/6] qemu-io: use BdrvRequestFlags instead of int Stefan Hajnoczi
2023-02-09 15:25 ` [Virtio-fs] [PULL 5/6] qemu-io: add -r option to register I/O buffer Stefan Hajnoczi
2023-02-09 15:25 ` [Virtio-fs] [PULL 6/6] iotests/detect-zeroes-registered-buf: add new test Stefan Hajnoczi
2023-02-10 10:49 ` [Virtio-fs] [PULL 0/6] Block patches Peter Maydell

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=20230209152520.434183-1-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-fs@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).