From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Adrian Moreno <amorenoz@redhat.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"Wang, Zhihong" <zhihong.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] vhost: add device reset status
Date: Fri, 7 Aug 2020 07:42:55 +0000 [thread overview]
Message-ID: <MN2PR11MB40632552A23D2A1D0B7952AF9C490@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <d24eff70-2b7c-fa5f-c84f-e46b25d6fb63@redhat.com>
Hi Adrian,
> -----Original Message-----
> From: Adrian Moreno <amorenoz@redhat.com>
> Sent: Thursday, August 6, 2020 7:59 PM
> To: Xia, Chenbo <chenbo.xia@intel.com>; dev@dpdk.org
> Cc: maxime.coquelin@redhat.com; Wang, Zhihong <zhihong.wang@intel.com>
> Subject: Re: [PATCH v1] vhost: add device reset status
>
>
>
> On 8/6/20 1:34 PM, Chenbo Xia wrote:
> > vhost lib now does not have definition of reset status. This patch
> > adds the reset status definiton and changes related log.
> >
> > Signed-off-by: Chenbo Xia <chenbo.xia@intel.com>
> > ---
> > lib/librte_vhost/vhost.h | 1 +
> > lib/librte_vhost/vhost_user.c | 2 ++
> > 2 files changed, 3 insertions(+)
> >
> > diff --git a/lib/librte_vhost/vhost.h b/lib/librte_vhost/vhost.h
> > index 632f66d53..73a1ed889 100644
> > --- a/lib/librte_vhost/vhost.h
> > +++ b/lib/librte_vhost/vhost.h
> > @@ -239,6 +239,7 @@ struct vhost_virtqueue {
> > } __rte_cache_aligned;
> >
> > /* Virtio device status as per Virtio specification */
> > +#define VIRTIO_DEVICE_STATUS_RESET 0x00
> > #define VIRTIO_DEVICE_STATUS_ACK 0x01
> > #define VIRTIO_DEVICE_STATUS_DRIVER 0x02
> > #define VIRTIO_DEVICE_STATUS_DRIVER_OK 0x04
> > diff --git a/lib/librte_vhost/vhost_user.c
> b/lib/librte_vhost/vhost_user.c
> > index c3c924fae..1b520ead7 100644
> > --- a/lib/librte_vhost/vhost_user.c
> > +++ b/lib/librte_vhost/vhost_user.c
> > @@ -2531,6 +2531,7 @@ vhost_user_set_status(struct virtio_net **pdev,
> struct VhostUserMsg *msg,
> > }
> >
> > VHOST_LOG_CONFIG(INFO, "New device status(0x%08x):\n"
> > + "\t-RESET: %u\n"
> > "\t-ACKNOWLEDGE: %u\n"
> > "\t-DRIVER: %u\n"
> > "\t-FEATURES_OK: %u\n"
> > @@ -2538,6 +2539,7 @@ vhost_user_set_status(struct virtio_net **pdev,
> struct VhostUserMsg *msg,
> > "\t-DEVICE_NEED_RESET: %u\n"
> > "\t-FAILED: %u\n",
> > dev->status,
> > + !!(dev->status & VIRTIO_DEVICE_STATUS_RESET),
>
> (dev->status & 0) will always be 0, right?
> how about (dev->status == VIRTIO_DEVICE_STATUS_RESET)?
Yes. Will correct this in v2.
Thanks!
Chenbo
>
> > !!(dev->status & VIRTIO_DEVICE_STATUS_ACK),
> > !!(dev->status & VIRTIO_DEVICE_STATUS_DRIVER),
> > !!(dev->status & VIRTIO_DEVICE_STATUS_FEATURES_OK),
> >
>
> --
> Adrián Moreno
next prev parent reply other threads:[~2020-08-07 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 11:34 Chenbo Xia
2020-08-06 11:58 ` Adrian Moreno
2020-08-07 7:42 ` Xia, Chenbo [this message]
2020-08-10 13:11 ` [dpdk-dev] [PATCH v2] " Chenbo Xia
2020-08-10 13:18 ` [dpdk-dev] [PATCH v3] " Chenbo Xia
2020-09-18 9:38 ` Maxime Coquelin
2020-09-18 12: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=MN2PR11MB40632552A23D2A1D0B7952AF9C490@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=amorenoz@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=zhihong.wang@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).