public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, Milton Miller <miltonm@bga.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Jamie Lokier <jamie@shareable.org>, Thomas Weber <swirl@gmx.li>,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio: remove virtio-pci root device
Date: Mon, 17 Jan 2011 11:03:51 +1030	[thread overview]
Message-ID: <201101171103.51778.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20110110171904.GA30058@redhat.com>

On Tue, 11 Jan 2011 03:49:04 am Michael S. Tsirkin wrote:
> On Mon, Jan 10, 2011 at 07:10:46PM +0200, Gleb Natapov wrote:
> > On Fri, Jan 07, 2011 at 02:55:06AM -0600, Milton Miller wrote:
> > > We sometimes need to map between the virtio device and
> > > the given pci device. One such use is OS installer that
> > > gets the boot pci device from BIOS and needs to
> > > find the relevant block device. Since it can't,
> > > installation fails.
> > > 
> > > Instead of creating a top-level devices/virtio-pci
> > > directory, create each device under the corresponding
> > > pci device node.  Symlinks to all virtio-pci
> > > devices can be found under the pci driver link in
> > > bus/pci/drivers/virtio-pci/devices, and all virtio
> > > devices under drivers/bus/virtio/devices.
> > > 
> > > Signed-off-by: Milton Miller <miltonm@bga.com>
> > Acked-by: Gleb Natapov <gleb@redhat.com>
> 
> Rusty, any comments?
> We are going to tell the installer guys that this
> is the interface, would be nice to know that the
> patch is queued before we do.

Yep, I've applied it.  Sorry, took a week off to work on my linux.conf.au
talk...

Cheers,
Rusty.

  reply	other threads:[~2011-01-17  0:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 19:17 [PATCH] virtio-pci: add softlinks between virtio and pci Michael S. Tsirkin
2011-01-05 19:28 ` Anthony Liguori
2011-01-05 19:38   ` Michael S. Tsirkin
2011-01-05 20:06     ` Anthony Liguori
2011-01-05 20:05   ` Michael S. Tsirkin
2011-01-05 20:08     ` Anthony Liguori
2011-01-05 21:15       ` Michael S. Tsirkin
2011-01-06  8:51 ` Gleb Natapov
2011-01-07  8:54 ` Milton Miller
2011-01-07  8:55   ` [PATCH] virtio: remove virtio-pci root device Milton Miller
2011-01-07 10:24     ` Michael S. Tsirkin
2011-01-09 15:18     ` Michael S. Tsirkin
2011-01-10 11:18       ` Gleb Natapov
2011-01-10 11:22         ` Michael S. Tsirkin
2011-01-10 11:27           ` Gleb Natapov
2011-01-10 11:42             ` Gleb Natapov
2011-01-10 12:08               ` Michael S. Tsirkin
2011-01-10 12:50                 ` Gleb Natapov
2011-01-10 13:31                   ` Michael S. Tsirkin
2011-01-10 13:40                     ` Gleb Natapov
2011-01-10 14:19                       ` Michael S. Tsirkin
2011-01-10 17:10     ` Gleb Natapov
2011-01-10 17:19       ` Michael S. Tsirkin
2011-01-17  0:33         ` Rusty Russell [this message]
2011-01-10 17:44     ` Michael S. Tsirkin

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=201101171103.51778.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=aliguori@us.ibm.com \
    --cc=gleb@redhat.com \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miltonm@bga.com \
    --cc=mst@redhat.com \
    --cc=swirl@gmx.li \
    --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