netdev - Re: [PATCH] virtio_net: add link status handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 09 Dec 2008 21:11:39 -0600
From:	Anthony Liguori <anthony@...emonkey.ws>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Mark McLoughlin <markmc@...hat.com>,
	netdev <netdev@...r.kernel.org>, kvm <kvm@...r.kernel.org>
Subject: Re: [PATCH] virtio_net: add link status handling

Rusty Russell wrote:
> On Wednesday 10 December 2008 08:02:14 Anthony Liguori wrote:
>   
>> Mark McLoughlin wrote:
>>     
>>> Allow the host to inform us that the link is down by adding
>>> a VIRTIO_NET_F_STATUS which indicates that device status is
>>> available in virtio_net config.
>>>
>>> This is currently useful for simulating link down conditions
>>> (e.g. using proposed qemu 'set_link' monitor command) but
>>> would also be needed if we were to support device assignment
>>> via virtio.
>>>       
>> It would be nice if the virtio-net card wrote some acknowledgement that 
>> it has received the link status down/up events.
>>     
>
> How about of every status change event? ie. a generic virtio_pci solution?
>   

A really simple way to do it would just be to have another status field 
that was the guest's status (verses the host requested status which the 
current field is).  All config reads/writes result in exits so it's easy 
to track.

Adding YA virtio event may be a little overkill.

Regards,

Anthony Liguori

> Rusty.
>   

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html