From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, Cindy Lu <lulu@redhat.com>
Subject: Re: [PATCH 0/2] vhost-vdpa: add trace functions in vhost-vdpa.c
Date: Mon, 21 Sep 2020 08:32:19 -0400 [thread overview]
Message-ID: <20200921083214-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200921084136.GB71121@stefanha-x1.localdomain>
On Mon, Sep 21, 2020 at 09:41:36AM +0100, Stefan Hajnoczi wrote:
> On Sun, Sep 20, 2020 at 06:24:32PM +0200, Laurent Vivier wrote:
> > Add trace events functions in vdpa functions.
> >
> > Modify qemu_hexdump() to be able to dump the vdpa config
> > in trace logs in hexadecimal form.
> >
> > Laurent Vivier (2):
> > util/hexdump: introduce qemu_hexdump_line()
> > vhost-vdpa: add trace-events
> >
> > hw/virtio/trace-events | 29 ++++++++++++++
> > hw/virtio/vhost-vdpa.c | 85 +++++++++++++++++++++++++++++++++++++++---
> > include/qemu-common.h | 8 ++++
> > util/hexdump.c | 54 +++++++++++++++++----------
> > 4 files changed, 151 insertions(+), 25 deletions(-)
>
> Please take this through the VIRTIO/vhost/vDPA tree:
>
> Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
Will do, tagged.
next prev parent reply other threads:[~2020-09-21 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 16:24 [PATCH 0/2] vhost-vdpa: add trace functions in vhost-vdpa.c Laurent Vivier
2020-09-20 16:24 ` [PATCH 1/2] util/hexdump: introduce qemu_hexdump_line() Laurent Vivier
2020-09-20 16:24 ` [PATCH 2/2] vhost-vdpa: add trace-events Laurent Vivier
2020-09-20 18:03 ` [PATCH 0/2] vhost-vdpa: add trace functions in vhost-vdpa.c no-reply
2020-09-21 12:29 ` Laurent Vivier
2020-09-21 8:41 ` Stefan Hajnoczi
2020-09-21 12:32 ` Michael S. Tsirkin [this message]
2020-09-21 12:42 ` Laurent Vivier
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=20200921083214-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--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).