From: Mark McLoughlin <markmc@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
netdev <netdev@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] virtio_net: add link status handling
Date: Wed, 07 Jan 2009 18:18:03 +0000 [thread overview]
Message-ID: <1231352283.5050.76.camel@localhost.localdomain> (raw)
In-Reply-To: <200812121834.49464.rusty@rustcorp.com.au>
Hi Rusty,
On Fri, 2008-12-12 at 18:34 +1030, Rusty Russell wrote:
> On Thursday 11 December 2008 05:04:44 Mark McLoughlin wrote:
> > On Tue, 2008-12-09 at 21:11 -0600, Anthony Liguori wrote:
> > > Rusty Russell wrote:
> > > > On Wednesday 10 December 2008 08:02:14 Anthony Liguori wrote:
> > > >> 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.
> >
> > Sounds very reasonable; that and Rusty's "mask out unknown bits"
> > suggestion in the version below.
>
> Not quite what I was after. I've taken the original patch, added the
> masking change. I'll test here and feed to DaveM.
This never got pushed to davem, did it? What you've got in your queue
looks fine to me ...
Cheers,
Mark.
next prev parent reply other threads:[~2009-01-07 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 10:19 [PATCH] virtio_net: add link status handling Mark McLoughlin
2008-12-09 21:32 ` Anthony Liguori
2008-12-09 23:53 ` Rusty Russell
2008-12-10 3:11 ` Anthony Liguori
2008-12-10 18:34 ` Mark McLoughlin
2008-12-12 8:04 ` Rusty Russell
2009-01-07 18:18 ` Mark McLoughlin [this message]
2009-01-09 11:51 ` Mark McLoughlin
2008-12-09 23:56 ` Rusty Russell
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=1231352283.5050.76.camel@localhost.localdomain \
--to=markmc@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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).