DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: dev@dpdk.org, 'Dyasly Sergey' <s.dyasly@samsung.com>
Subject: Re: [dpdk-dev] PING: [PATCH v2] pmd/virtio: fix cannot start virtio dev after stop
Date: Thu, 4 Feb 2016 15:08:24 +0000	[thread overview]
Message-ID: <20160204150824.GA14468@bricha3-MOBL3> (raw)
In-Reply-To: <00b201d15f36$e87e0260$b97a0720$@samsung.com>

On Thu, Feb 04, 2016 at 01:29:19PM +0300, Pavel Fedin wrote:
>  Hello! Are there any news about this patch? We have got this problem for the second time, it reproduces every time we try to use
> ovs-dpdk inside virtual machine with virtio-net adapter.
> 
> Kind regards,
> Pavel Fedin
> Senior Engineer
> Samsung Electronics Research center Russia
> 
> 

Commited to dpdk-next-net/rel_16_04 with added fixes line.

/Bruce


> > -----Original Message-----
> > From: Jianfeng Tan [mailto:jianfeng.tan@intel.com]
> > Sent: Monday, January 11, 2016 9:16 AM
> > To: dev@dpdk.org
> > Cc: p.fedin@samsung.com; yuanhan.liu@linux.intel.com; Jianfeng Tan
> > Subject: [PATCH v2] pmd/virtio: fix cannot start virtio dev after stop
> > 
> > v2 changes:
> >     - Address compiling error.
> >     - Add Reported-by.
> > 
> > Fix the issue that virtio device cannot be started after stopped.
> > 
> > The field, hw->started, should be changed by virtio_dev_start/stop instead
> > of virtio_dev_close.
> > 
> > Reported-by: Pavel Fedin <p.fedin@samsung.com>
> > Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> > Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> > 

      parent reply	other threads:[~2016-02-04 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 10:29 Pavel Fedin
2016-02-04 13:39 ` Yuanhan Liu
2016-02-04 15:08 ` Bruce Richardson [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=20160204150824.GA14468@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=p.fedin@samsung.com \
    --cc=s.dyasly@samsung.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).