qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, Alexey Kardashevskiy <aik@ozlabs.ru>,
	qemu-devel@nongnu.org, Alex Graf <agraf@suse.de>,
	anthony@codemonkey.ws, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] vfio with iommu groups
Date: Mon, 14 May 2012 14:29:20 +1000	[thread overview]
Message-ID: <1336969760.6727.17.camel@pasglop> (raw)
In-Reply-To: <1336968971.6954.41.camel@bling.home>

On Sun, 2012-05-13 at 22:16 -0600, Alex Williamson wrote:
> > However theoretically we might want to show these 3 PCIe bridges as well (but not the root complex).
> > For example, INTx lines should be swizzled when the guest parses a device tree and
> > tries to calculate a real IRQ number. VFIO does not handles bridges at all, it treats them as PCI
> > functions.
> > 
> > Is there any idea what to do with bridges?
> 
> I don't really have a problem with the idea of exposing bridges, but it
> get's pretty complicated.  What happens if the guest reprograms the
> subordinate bus numbers?  Is there any advantage vs exposing an emulated
> bridge in it's place?  Do you have a proposal for it?  Thanks,

I think exposing an emulated bridge would be more in the "spirit" of the
current vfio and safer for now (long run, as we already discussed, we
might look at an other option with more direct HW access for power).

We do want to expose those bridges one way or another for the sake of
getting the interrupt routing right, since the guest will make
assumptions based on those bridges to calculate the proper swizzling.

Cheers,
Ben.

      reply	other threads:[~2012-05-14  4:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-12  7:31 [Qemu-devel] vfio with iommu groups Alexey Kardashevskiy
2012-05-14  4:16 ` Alex Williamson
2012-05-14  4:29   ` Benjamin Herrenschmidt [this message]

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=1336969760.6727.17.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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).