virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: [RFC 1/4] New virtio bus driver
Date: Mon, 09 Jul 2007 09:42:13 +1000	[thread overview]
Message-ID: <1183938133.6005.372.camel@localhost.localdomain> (raw)
In-Reply-To: <200707082229.00810.arnd@arndb.de>

On Sun, 2007-07-08 at 22:29 +0200, Arnd Bergmann wrote:
> On Sunday 08 July 2007, Avi Kivity wrote:
> 
> > > Alternatively, we could have a mechanism separate from the
> > > virtqueue concept, like a synchronous get_config_data/set_config_data
> > > callback into the host driver.
> > >   
> > 
> > You also need to allow the host to notify the guest about configuration 
> > changes.
> 
> That is much harder to do, it would require a separate interrupt if you
> want to have a device independent mechanism.

See, I was going to have a "virtblk_device_change()" entry point and
leave others to solve the problem of how to connect it up...

TBH I think it's a little early to design the One True Bus: I'm just not
smart enough to see so far ahead.  When we have a bundle of devices
which support a most of the functionality we want, I think we'll have a
better idea of how to encapsulate it.

(That said, I love that Arnd is thinking about this now: it will make it
much easier when we do reach that point).

Cheers,
Rusty.

  reply	other threads:[~2007-07-08 23:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 12:42 [RFC 0/4] Using a generic bus_type for virtio arnd
2007-07-06 12:42 ` [RFC 1/4] New virtio bus driver arnd
2007-07-08  9:59   ` Avi Kivity
2007-07-08 15:29     ` Arnd Bergmann
2007-07-08 15:48       ` Avi Kivity
2007-07-08 20:29         ` Arnd Bergmann
2007-07-08 23:42           ` Rusty Russell [this message]
2007-07-09  6:49           ` Avi Kivity
2007-07-09 11:18             ` Arnd Bergmann
2007-07-09 11:41               ` Avi Kivity
2007-07-09 11:38                 ` Arnd Bergmann
2007-07-09 12:09                   ` Avi Kivity
2007-07-09 14:24                     ` Arnd Bergmann
2007-07-09 14:56                       ` Avi Kivity
2007-07-09 16:33                         ` Arnd Bergmann
2007-07-10  1:53                     ` Rusty Russell
2007-07-10  7:56                       ` Avi Kivity
2007-07-10  1:17             ` Rusty Russell
2007-07-10  6:06               ` Avi Kivity
2007-07-06 12:42 ` [RFC 2/4] Convert virtio_net to new virtio bus arnd
2007-07-06 12:42 ` [RFC 3/4] Convert virtio_blk " arnd
2007-07-06 12:42 ` [RFC 4/4] Example virtio host implementation, using chardev arnd
2007-07-08  2:15 ` [RFC 0/4] Using a generic bus_type for virtio Rusty Russell
2007-07-08  9:45   ` Avi Kivity
2007-07-08 15:55   ` Arnd Bergmann
2007-07-08  9:42 ` Avi Kivity

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=1183938133.6005.372.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=arnd@arndb.de \
    --cc=virtualization@lists.linux-foundation.org \
    /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).