From: manish jaggi <manishjaggi.oss@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Julien Grall <julien.grall@linaro.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Prasun Kapoor <prasun.Kapoor@caviumnetworks.com>,
manish.jaggi@caviumnetworks.com,
Ryan Wilson <hap9@epoch.ncsc.mil>,
xen-devel <xen-devel@lists.xen.org>,
psawargaonkar@linaro.org, Anup Patel <anup.patel@linaro.org>
Subject: Re: [RFC + Queries] Flow of PCI passthrough in ARM
Date: Mon, 20 Oct 2014 19:00:49 +0530 [thread overview]
Message-ID: <CAAiw7Jmq0zRHfv0VtyyFwJKzr5UsCd1wucSFDfY1d4xmisZ-zQ@mail.gmail.com> (raw)
In-Reply-To: <20141008145107.GC18573@laptop.dumpdata.com>
On 8 October 2014 20:21, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> On Wed, Oct 08, 2014 at 07:17:48PM +0530, manish jaggi wrote:
>> On 8 October 2014 19:15, Ian Campbell <Ian.Campbell@citrix.com> wrote:
>> > On Wed, 2014-10-08 at 19:07 +0530, manish jaggi wrote:
>> >> Thanks for replying. As detailed in this thread, I need to create a
>> >> hypercall that would send the following information to Xen at the time
>> >> of PCI attach
>> >> { sbdf , domU sbdf, domainId }.
>> >> I am not able to find a way to get the domU sbdf from dom0 at the time
>> >> of pci-attach.
>> >
>> > I think it would need to be done by the pciback driver in the dom0
>> > kernel, which AFAIK is the thing which consistently knows both physical
>> > and virtual sbdf for a given assigned device.
>> >
>> > Ian.
>> >
>> Correct, can you point out which data structure holds the domU sbdf
>> corresponding to the actual sbdf in pciback.
>
> See 'xen_pcibk_export_device' or 'xen_pcibk_publish_pci_root'
> is that what you are referring to?
Xen docs also mention about xen-pciback.passthrough=1. If I set this
in dom0 i see that the device is enumerated as the same sbdf in domU,
but
a) it is not shown in lspci
b) no front-back communication is done for reading devices configuration space
.
Is option useful / fully implemented for ARM ?
next prev parent reply other threads:[~2014-10-20 13:30 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
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 [this message]
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=CAAiw7Jmq0zRHfv0VtyyFwJKzr5UsCd1wucSFDfY1d4xmisZ-zQ@mail.gmail.com \
--to=manishjaggi.oss@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=anup.patel@linaro.org \
--cc=hap9@epoch.ncsc.mil \
--cc=julien.grall@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=manish.jaggi@caviumnetworks.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).