From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Marc Marí" <marc.mari.barcelo@gmail.com>
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 0/5] libqos: Virtio MMIO driver
Date: Wed, 25 Feb 2015 11:08:31 +0000 [thread overview]
Message-ID: <20150225110831.GH18680@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1424812915-25728-1-git-send-email-marc.mari.barcelo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
On Tue, Feb 24, 2015 at 10:21:50PM +0100, Marc Marí wrote:
> Add virtio-mmio support to libqos and test case for virtio-blk.
>
> Changes for version 3:
> - Fix leaks and minor bugs
> - Extract basic test case to a function
>
> Changes for version 4:
> - Add format=raw to images, to avoid warnings
> - Solve bug with timeout in interrupt checking in virtio MMIO due to a race
> condition
>
> Changes for version 5:
> - Change function generic_alloc_init_flags in tests/libqos/malloc-generic.c to
> compile with changes from commit f6f363c1f4f962aee9f69c67ab2f3ff58c30f8c1.
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> Marc Marí (5):
> libqos: Change use of pointers to uint64_t in virtio
> tests: Prepare virtio-blk-test for multi-arch implementation
> libqos: Remove PCI assumptions in constants of virtio driver
> libqos: Add malloc generic
> libqos: Add virtio MMIO support
>
> tests/Makefile | 4 +-
> tests/libqos/malloc-generic.c | 39 +++++++
> tests/libqos/malloc-generic.h | 21 ++++
> tests/libqos/virtio-mmio.c | 198 +++++++++++++++++++++++++++++++
> tests/libqos/virtio-mmio.h | 46 ++++++++
> tests/libqos/virtio-pci.c | 50 ++++----
> tests/libqos/virtio-pci.h | 24 ++--
> tests/libqos/virtio.c | 8 +-
> tests/libqos/virtio.h | 16 +--
> tests/virtio-blk-test.c | 259 ++++++++++++++++++++++++++++-------------
> 10 files changed, 537 insertions(+), 128 deletions(-)
> create mode 100644 tests/libqos/malloc-generic.c
> create mode 100644 tests/libqos/malloc-generic.h
> create mode 100644 tests/libqos/virtio-mmio.c
> create mode 100644 tests/libqos/virtio-mmio.h
>
> --
> 1.7.10.4
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-02-25 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 21:21 [Qemu-devel] [PATCH v5 0/5] libqos: Virtio MMIO driver Marc Marí
2015-02-24 21:21 ` [Qemu-devel] [PATCH v5 1/5] libqos: Change use of pointers to uint64_t in virtio Marc Marí
2015-02-24 21:21 ` [Qemu-devel] [PATCH v5 2/5] tests: Prepare virtio-blk-test for multi-arch implementation Marc Marí
2015-02-24 21:21 ` [Qemu-devel] [PATCH v5 3/5] libqos: Remove PCI assumptions in constants of virtio driver Marc Marí
2015-02-24 21:21 ` [Qemu-devel] [PATCH v5 4/5] libqos: Add malloc generic Marc Marí
2015-02-25 10:50 ` Stefan Hajnoczi
2015-02-24 21:21 ` [Qemu-devel] [PATCH v5 5/5] libqos: Add virtio MMIO support Marc Marí
2015-02-25 11:08 ` Stefan Hajnoczi [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=20150225110831.GH18680@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).