From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anup Patel <anup.patel@linaro.org>,
Vijay Kilari <vijay.kilari@gmail.com>,
Prasun Kapoor <prasun.Kapoor@caviumnetworks.com>,
manish.jaggi@caviumnetworks.com,
Julien Grall <julien.grall@linaro.org>,
xen-devel <xen-devel@lists.xen.org>,
psawargaonkar@linaro.org, Matt.Evans@arm.com,
Dave.Martin@arm.com, manish jaggi <manishjaggi.oss@gmail.com>
Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM
Date: Mon, 6 Oct 2014 16:38:03 +0100 [thread overview]
Message-ID: <1412609883.14255.18.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1410061452000.17038@kaball.uk.xensource.com>
On Mon, 2014-10-06 at 15:11 +0100, Stefano Stabellini wrote:
> Actually the xen-pcifront driver in the guest knows the real PCI sbdf
> for the assigned device, not just the virtual slot. On x86 xen-pcifront
> makes an hypercall to enable msi/msix on the device passing the real
> sbdf as argument:
>
> drivers/pci/xen-pcifront.c:pci_frontend_enable_msix
>
> Could we use the same hypercall to enable msi/msix on ARM? That would be
> ideal.
That's not a hypercall, it's a message to pciback.
And I think it takes the virtual BDF, since pciback knows how to
translate such things.
> Otherwise xen-pcifront could call a new hypercall to let Xen know the
> virtual sbdf to sbdf mapping. But I would prefer not to introduce a new
> hypercall and reuse the existing one.
Ian.
next prev parent reply other threads:[~2014-10-06 15:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 11:34 [RFC + Queries] Flow of PCI passthrough in ARM manish jaggi
2014-09-22 10:45 ` Stefano Stabellini
2014-09-22 11:09 ` Ian Campbell
2014-09-24 10:56 ` manish jaggi
2014-09-24 10:53 ` manish jaggi
2014-09-24 12:13 ` Jan Beulich
2014-09-24 14:10 ` Stefano Stabellini
2014-09-24 18:32 ` manish jaggi
2014-09-25 10:27 ` Stefano Stabellini
2014-10-01 10:37 ` manish jaggi
2014-10-02 16:41 ` Stefano Stabellini
2014-10-02 16:59 ` Stefano Stabellini
2014-10-03 9:01 ` Ian Campbell
2014-10-03 9:33 ` manish jaggi
2014-10-03 9:32 ` manish jaggi
2014-10-06 11:05 ` manish jaggi
2014-10-06 14:11 ` Stefano Stabellini
2014-10-06 15:38 ` Ian Campbell [this message]
2014-10-06 17:39 ` manish jaggi
2014-10-06 17:39 ` manish jaggi
2014-10-07 18:17 ` Stefano Stabellini
2014-10-08 11:46 ` manish jaggi
2014-10-08 12:46 ` Konrad Rzeszutek Wilk
2014-10-08 13:37 ` manish jaggi
2014-10-08 13:45 ` Ian Campbell
2014-10-08 13:47 ` manish jaggi
2014-10-08 13:58 ` Ian Campbell
2014-10-08 14:51 ` Konrad Rzeszutek Wilk
2014-10-20 13:30 ` manish jaggi
2014-10-20 14:54 ` Stefano Stabellini
2014-11-06 15:28 ` manish jaggi
2014-11-06 15:48 ` Stefano Stabellini
2014-11-06 15:55 ` manish jaggi
2014-11-06 16:02 ` Julien Grall
2014-11-06 16:07 ` Stefano Stabellini
2014-11-06 16:20 ` manish jaggi
2014-11-07 10:29 ` Julien Grall
2014-11-06 19:41 ` Konrad Rzeszutek Wilk
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=1412609883.14255.18.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Dave.Martin@arm.com \
--cc=Matt.Evans@arm.com \
--cc=anup.patel@linaro.org \
--cc=julien.grall@linaro.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=manishjaggi.oss@gmail.com \
--cc=prasun.Kapoor@caviumnetworks.com \
--cc=psawargaonkar@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vijay.kilari@gmail.com \
--cc=xen-devel@lists.xen.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).