public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Alex Chiang <achiang@hp.com>,
	jbarnes@virtuousgeek.org, linux-arch@vger.kernel.org,
	Kyle McMartin <kyle@mcmartin.ca>, Tony Luck <tony.luck@intel.com>,
	Russell King <linux@arm.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jeff Dike <jdike@addtoit.com>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	David Howells <dhowells@redhat.com>,
	Paul Mundt <lethal@linux-sh.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Ingo Molnar <mingo@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] PCI: remove pcibios_scan_all_fns()
Date: Mon, 22 Jun 2009 12:30:57 -0600	[thread overview]
Message-ID: <20090622183056.GY19977@parisc-linux.org> (raw)
In-Reply-To: <4A3FCB68.3030004@goop.org>

On Mon, Jun 22, 2009 at 11:20:24AM -0700, Jeremy Fitzhardinge wrote:
> > I'd like to know what the KVM / Xen / ... people think about this.
> > I don't know if they rely on function 5 being able to show up out of
> > the blue.
> 
> We want to be able to export specific functions to a particular domain,
> so it might see a PCI device with only function 5.
> 
> It looks like we lose that ability with this patch, is that right?

That would be correct.  I'm guessing your out-of-tree code sets
pcibios_scan_all_fns()?

Now, there are various options.  One is that you could remap config
space accesses -- domain:bus:dev.fn in the guest don't have to match
domain:bus:dev.fn in the host.  That's a certain amount of overhead in
every config space access, but it doesn't have to be a large one.

Another would be that you could create dummy devices in the guest at
function 0, and then the guest would scan all the functions.  A little
ugly, perhaps.

A third would be for guests to not do this scanning at all.  You could
present the devices through something like the openfirmware tree, and
create them insteaqd of scanning for them.  If you care about startup
time, this is probably the way to go.

There's probably other ways I haven't thought of ...

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-06-22 18:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 14:08 [PATCH] PCI: remove pcibios_scan_all_fns() Alex Chiang
2009-06-22 14:21 ` Kyle McMartin
2009-06-22 14:26 ` Ralf Baechle
2009-06-22 14:36   ` Matthew Wilcox
2009-06-22 14:34 ` Matthew Wilcox
2009-06-22 18:20   ` Jeremy Fitzhardinge
2009-06-22 18:30     ` Matthew Wilcox [this message]
2009-06-22 23:40       ` Benjamin Herrenschmidt
2009-06-23 19:08         ` Matthew Wilcox
2009-06-23 20:34           ` Jeremy Fitzhardinge
2009-06-23 20:56             ` Matthew Wilcox
2009-06-23 21:49             ` Benjamin Herrenschmidt
2009-06-23 22:24               ` Jeremy Fitzhardinge
2009-06-23 22:41                 ` Benjamin Herrenschmidt
2009-06-23 22:53                   ` Jeremy Fitzhardinge
2009-06-24  0:02                     ` Benjamin Herrenschmidt
2009-06-24 10:30             ` Ian Campbell
2009-06-23 21:47           ` Benjamin Herrenschmidt
2009-06-22 23:55       ` Jeremy Fitzhardinge
2009-06-23  0:33         ` Benjamin Herrenschmidt
2009-06-23  1:43   ` Chris Wright
2009-06-23  2:22     ` Benjamin Herrenschmidt
2009-06-23 18:29   ` Avi Kivity
2009-06-22 15:29 ` Russell King - ARM Linux
2009-06-22 16:53 ` Arnd Bergmann
2009-06-23 16:43 ` Paul Mundt
2009-06-29 20:33 ` Jesse Barnes

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=20090622183056.GY19977@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=achiang@hp.com \
    --cc=arnd@arndb.de \
    --cc=avi@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jdike@addtoit.com \
    --cc=jeremy@goop.org \
    --cc=kyle@mcmartin.ca \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=tony.luck@intel.com \
    --cc=ysato@users.sourceforge.jp \
    /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