From: David Marchand <david.marchand@redhat.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3 0/9] vhost: improve logging
Date: Thu, 27 Jan 2022 09:09:16 +0100 [thread overview]
Message-ID: <CAJFAV8wY7Wnt4U76+M-S-Q43QA2+W5PF-QvQHGok_OC0hRa+Xw@mail.gmail.com> (raw)
In-Reply-To: <SN6PR11MB350432B45E7592A469CA40209C219@SN6PR11MB3504.namprd11.prod.outlook.com>
On Thu, Jan 27, 2022 at 6:37 AM Xia, Chenbo <chenbo.xia@intel.com> wrote:
> > From: Maxime Coquelin <maxime.coquelin@redhat.com>
> >
> > This series aims at easing Vhost logs analysis, by
> > prepending the Vhost-user socket path to all logs and to
> > remove multi-line comments. Doing so, filtering Vhost-user
> > ports logs is much easier.
> >
> > Changes in v3:
> > ==============
> > - Fix various typos reported (Chenbo)
> > - Revert one multi-line comment removal (Chenbo)
> >
> > Changes in v2:
> > ==============
> > - Add missing socket paths (David)
> > - avoid identical logs in iotlb code (David)
> > - Use data log type when used in datapath (David)
> >
> > Maxime Coquelin (9):
> > vhost: improve IOTLB logs
> > vhost: improve vDPA registration failure log
> > vhost: improve Vhost layer logs
> > vhost: improve Vhost-user layer logs
> > vhost: improve socket layer logs
> > vhost: improve Virtio-net layer logs
> > vhost: remove multi-line logs
> > vhost: differentiate IOTLB logs
> > vhost: use proper logging type for data path
> >
> > lib/vhost/iotlb.c | 30 +-
> > lib/vhost/iotlb.h | 10 +-
> > lib/vhost/socket.c | 148 ++++-----
> > lib/vhost/vdpa.c | 4 +-
> > lib/vhost/vhost.c | 108 ++++---
> > lib/vhost/vhost_user.c | 678 ++++++++++++++++++++---------------------
> > lib/vhost/vhost_user.h | 4 +-
> > lib/vhost/virtio_net.c | 165 +++++-----
> > 8 files changed, 548 insertions(+), 599 deletions(-)
> >
> > --
> > 2.34.1
>
> Series applied to next-virtio/main, thanks
For the series:
Reviewed-by: David Marchand <david.marchand@redhat.com>
--
David Marchand
prev parent reply other threads:[~2022-01-27 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 9:55 Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 1/9] vhost: improve IOTLB logs Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 2/9] vhost: improve vDPA registration failure log Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 3/9] vhost: improve Vhost layer logs Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 4/9] vhost: improve Vhost-user " Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 5/9] vhost: improve socket " Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 6/9] vhost: improve Virtio-net " Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 7/9] vhost: remove multi-line logs Maxime Coquelin
2022-01-27 4:57 ` Xia, Chenbo
2022-01-26 9:55 ` [PATCH v3 8/9] vhost: differentiate IOTLB logs Maxime Coquelin
2022-01-26 9:55 ` [PATCH v3 9/9] vhost: use proper logging type for data path Maxime Coquelin
2022-01-27 5:37 ` [PATCH v3 0/9] vhost: improve logging Xia, Chenbo
2022-01-27 8:09 ` David Marchand [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=CAJFAV8wY7Wnt4U76+M-S-Q43QA2+W5PF-QvQHGok_OC0hRa+Xw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@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).