From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Fam Zheng <fam@euphon.net>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 0/9] util/vfio-helpers: Improve debugging experience
Date: Wed, 14 Oct 2020 14:42:47 +0200 [thread overview]
Message-ID: <81d80fdd-e2f2-db5c-f358-e28eeb291c82@redhat.com> (raw)
In-Reply-To: <9d08c9ab6310a5f0c796c4d98d1c51f071802369.camel@euphon.net>
On 10/14/20 2:34 PM, Fam Zheng wrote:
> On Wed, 2020-10-14 at 13:52 +0200, Philippe Mathieu-Daudé wrote:
>> A bunch of boring patches that have been proven helpful
>> while debugging.
>>
>> Philippe Mathieu-Daudé (9):
>> 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: Let qemu_vfio_dma_map() propagate Error
>> util/vfio-helpers: Let qemu_vfio_do_mapping() propagate Error
>> util/vfio-helpers: Let qemu_vfio_verify_mappings() use
>> error_report()
>>
>> include/qemu/vfio-helpers.h | 2 +-
>> block/nvme.c | 14 ++++----
>> util/vfio-helpers.c | 66 +++++++++++++++++++++------------
>> ----
>> util/trace-events | 10 ++++--
>> 4 files changed, 54 insertions(+), 38 deletions(-)
>>
>> --
>> 2.26.2
>>
>>
>>
>
> Modular the g_strdup_printf() memleak I pointed out:
>
> Reviewed-by: Fam Zheng <fam@euphon.net>
Thanks!
next prev parent reply other threads:[~2020-10-14 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 11:52 [PATCH 0/9] util/vfio-helpers: Improve debugging experience Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 1/9] util/vfio-helpers: Improve reporting unsupported IOMMU type Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 2/9] util/vfio-helpers: Trace PCI I/O config accesses Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 3/9] util/vfio-helpers: Trace PCI BAR region info Philippe Mathieu-Daudé
2020-10-14 12:23 ` Fam Zheng
2020-10-14 12:42 ` Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 4/9] util/vfio-helpers: Trace where BARs are mapped Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 5/9] util/vfio-helpers: Improve DMA trace events Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 6/9] util/vfio-helpers: Convert vfio_dump_mapping to " Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 7/9] util/vfio-helpers: Let qemu_vfio_dma_map() propagate Error Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 8/9] util/vfio-helpers: Let qemu_vfio_do_mapping() " Philippe Mathieu-Daudé
2020-10-14 11:52 ` [PATCH 9/9] util/vfio-helpers: Let qemu_vfio_verify_mappings() use error_report() Philippe Mathieu-Daudé
2020-10-14 12:34 ` [PATCH 0/9] util/vfio-helpers: Improve debugging experience Fam Zheng
2020-10-14 12:42 ` Philippe Mathieu-Daudé [this message]
2020-10-14 12:50 ` Fam Zheng
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=81d80fdd-e2f2-db5c-f358-e28eeb291c82@redhat.com \
--to=philmd@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 NNTP newsgroup(s).