qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <fam@euphon.net>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Max Reitz <mreitz@redhat.com>, Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH-for-5.2 v3 0/7] util/vfio-helpers: Generic code strengthening
Date: Tue, 3 Nov 2020 17:37:43 +0000	[thread overview]
Message-ID: <20201103173743.GD259481@stefanha-x1.localdomain> (raw)
In-Reply-To: <20201103020733.2303148-1-philmd@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

On Tue, Nov 03, 2020 at 03:07:26AM +0100, Philippe Mathieu-Daudé wrote:
> v3:
> - Extract reviewed patches from
>   "util/vfio-helpers: Allow using multiple MSIX IRQs"
> - Added "Assert offset is aligned to page size"
>   which would have helped debugging:
>   "block/nvme: Fix use of write-only doorbells page on Aarch64 arch"
> 
> Missing review: 7
> 
> Based-on: <20201029093306.1063879-1-philmd@redhat.com>
> 
> Philippe Mathieu-Daudé (7):
>   util/vfio-helpers: Improve reporting unsupported IOMMU type
>   util/vfio-helpers: Trace PCI I/O config accesses
>   util/vfio-helpers: Trace PCI BAR region info
>   util/vfio-helpers: Trace where BARs are mapped
>   util/vfio-helpers: Improve DMA trace events
>   util/vfio-helpers: Convert vfio_dump_mapping to trace events
>   util/vfio-helpers: Assert offset is aligned to page size
> 
>  util/vfio-helpers.c | 43 ++++++++++++++++++++++++++-----------------
>  util/trace-events   | 10 ++++++++--
>  2 files changed, 34 insertions(+), 19 deletions(-)
> 
> -- 
> 2.26.2
> 
> 

Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-11-03 17:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03  2:07 [PATCH-for-5.2 v3 0/7] util/vfio-helpers: Generic code strengthening Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 1/7] util/vfio-helpers: Improve reporting unsupported IOMMU type Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 2/7] util/vfio-helpers: Trace PCI I/O config accesses Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 3/7] util/vfio-helpers: Trace PCI BAR region info Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 4/7] util/vfio-helpers: Trace where BARs are mapped Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 5/7] util/vfio-helpers: Improve DMA trace events Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 6/7] util/vfio-helpers: Convert vfio_dump_mapping to " Philippe Mathieu-Daudé
2020-11-03  2:07 ` [PATCH-for-5.2 v3 7/7] util/vfio-helpers: Assert offset is aligned to page size Philippe Mathieu-Daudé
2020-11-03 17:37 ` Stefan Hajnoczi [this message]
2020-11-03 18:37 ` [PATCH-for-5.2 v3 0/7] util/vfio-helpers: Generic code strengthening Auger Eric

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=20201103173743.GD259481@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).