On Mon, Jan 29, 2018 at 10:24 AM, Michael S. Tsirkin wrote:
> On Sun, Jan 28, 2018 at 08:26:53PM -0800, Alexander Duyck wrote:
>> >> > For live migration with advanced usecases that Siwei is suggesting, i
>> >> > think we need a new driver with a new device type that can track the
>> >> > VF speci
On Sun, Jan 28, 2018 at 3:02 PM, Stephen Hemminger
wrote:
> On Fri, 26 Jan 2018 18:30:03 -0800
> Jakub Kicinski wrote:
>
>> On Fri, 26 Jan 2018 15:30:35 -0800, Samudrala, Sridhar wrote:
>> > On 1/26/2018 2:47 PM, Jakub Kicinski wrote:
>> > > On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin
On 2018年01月24日 00:03, Samudrala, Sridhar wrote:
On 1/23/2018 2:33 AM, Jason Wang wrote:
On 2018年01月12日 13:58, Sridhar Samudrala wrote:
static netdev_tx_t start_xmit(struct sk_buff *skb, struct
net_device *dev)
{
struct virtnet_info *vi = netdev_priv(dev);
int qnum = skb_g
From: Jason Wang
Date: Thu, 25 Jan 2018 22:03:52 +0800
> We don't stop device before reset owner, this means we could try to
> serve any virtqueue kick before reset dev->worker. This will result a
> warn since the work was pending at llist during owner resetting. Fix
> this by stopping device dur
On Sun, Jan 28, 2018 at 08:26:53PM -0800, Alexander Duyck wrote:
> >> > For live migration with advanced usecases that Siwei is suggesting, i
> >> > think we need a new driver with a new device type that can track the
> >> > VF specific feature settings even when the VF driver is unloaded.
> >
> >