From: "Wang, Xiao W" <xiao.w.wang@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Bie, Tiwei" <tiwei.bie@intel.com>,
"Yao, Lei A" <lei.a.yao@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/virtio-user: fix dev_init in legacy-mem mode
Date: Thu, 17 May 2018 08:07:08 +0000 [thread overview]
Message-ID: <B7F2E978279D1D49A3034B7786DACF406F8BDB7A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <77d27fbb-710a-3b4b-43e7-30776529c83e@redhat.com>
Hi,
> -----Original Message-----
> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> Sent: Thursday, May 17, 2018 4:03 PM
> To: Wang, Xiao W <xiao.w.wang@intel.com>
> Cc: dev@dpdk.org; Bie, Tiwei <tiwei.bie@intel.com>; Yao, Lei A
> <lei.a.yao@intel.com>
> Subject: Re: [PATCH] net/virtio-user: fix dev_init in legacy-mem mode
>
> Hi Xiao,
>
> Next time, could you please devtools/check-git-log.sh script before
> posting.
OK, thanks!
BRs,
Xiao
>
> I tihnk the commit title should be changed to:
> net/virtio-user: fix device init in legacy-mem mode
>
> On 05/17/2018 09:35 AM, Xiao Wang wrote:
> > In legacy-mem mode, memory event callback registering is not supported,
> > we should not return error in dev_init on this case.
> >
> > Fixes: 12ecb2f63b12 ("net/virtio-user: support memory hotplug")
> >
> > Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
> > Suggested-by: Tiwei Bie <tiwei.bie@intel.com>
>
> I think the suggested-by line should go above the signed-off one,
> as it was suggested before being implemented.
>
> > ---
> > drivers/net/virtio/virtio_user/virtio_user_dev.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/virtio/virtio_user/virtio_user_dev.c
> b/drivers/net/virtio/virtio_user/virtio_user_dev.c
> > index 992a68757..bd16fbb60 100644
> > --- a/drivers/net/virtio/virtio_user/virtio_user_dev.c
> > +++ b/drivers/net/virtio/virtio_user/virtio_user_dev.c
> > @@ -445,8 +445,11 @@ virtio_user_dev_init(struct virtio_user_dev *dev,
> char *path, int queues,
> >
> > if
> (rte_mem_event_callback_register(VIRTIO_USER_MEM_EVENT_CLB_NAME,
> > virtio_user_mem_event_cb, dev)) {
> > - PMD_INIT_LOG(ERR, "Failed to register mem event
> callback\n");
> > - return -1;
> > + if (rte_errno != ENOTSUP) {
> > + PMD_INIT_LOG(ERR, "Failed to register mem event"
> > + " callback\n");
> > + return -1;
> > + }
> > }
> >
> > return 0;
> >
>
> Apart above minor comments, the patch looks good to me:
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> I'll handle the changes when applying.
>
> Thanks,
> Maxime
next prev parent reply other threads:[~2018-05-17 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:35 Xiao Wang
2018-05-17 8:03 ` Maxime Coquelin
2018-05-17 8:07 ` Wang, Xiao W [this message]
2018-05-17 8:28 ` Maxime Coquelin
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=B7F2E978279D1D49A3034B7786DACF406F8BDB7A@SHSMSX101.ccr.corp.intel.com \
--to=xiao.w.wang@intel.com \
--cc=dev@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.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).