This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH] netfront: support ethtool's get_link()

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH] netfront: support ethtool's get_link()
From: Mark McLoughlin <markmc@xxxxxxxxxx>
Date: Mon, 17 Jul 2006 10:30:26 +0100
Delivery-date: Mon, 17 Jul 2006 02:30:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1152890168.12312.5.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1152890168.12312.5.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
        I hadn't spotted that netfront already supports some ethtool ops. That
was just dumb; apologies.

        More correct patch attached.


On Fri, 2006-07-14 at 16:16 +0100, Mark McLoughlin wrote:
> Hi,
>       Attached is a very simple patch to support ethtool's get_link()
> operation. This allows things like NetworkManager's and anaconda's
> carrier detection code to work with netfront.
>       It seems sane to take the simple approach of reporting the link as
> active as soon as we've connected to the backend device. It's irrelevant
> whether the physical device in dom0 has link, since there could well be
> someone else on the bridge responding.

Attachment: xennet-ethtool-get-link.patch
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>