From: Julien Grall <julien.grall@citrix.com>
To: "Ian Campbell" <ian.campbell@citrix.com>,
"Manish Jaggi" <mjaggi@caviumnetworks.com>,
"Xen Devel" <xen-devel@lists.xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"★ Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
"\"Manish Jaggi,★ Kumar,
Vijaya\"" <Vijaya.Kumar@caviumnetworks.com>,
"Julien Grall" <julien.grall@linaro.org>
Cc: "Prasun.kapoor@cavium.com" <Prasun.kapoor@cavium.com>
Subject: Re: PCI Pass-through in Xen ARM: Draft 4
Date: Wed, 2 Sep 2015 16:40:45 +0100 [thread overview]
Message-ID: <55E7187D.2090901@citrix.com> (raw)
In-Reply-To: <1441207163.26292.248.camel@citrix.com>
On 02/09/15 16:19, Ian Campbell wrote:
> On Thu, 2015-08-13 at 11:37 +0100, Julien Grall wrote:
>>> 4.2.2 Xenstore Update: For each PCI-EP BAR (IPA-PA mapping info).
>>> ----------------------------------------------------------------------
>>> ------
>>>
>>> Toolstack also updates the xenstore information for the device
>>> (virtualbar:physical bar).This information is read by xen-pciback and
>>> returned to the domU-pcifront driver configuration space reads for
>>> BAR.
>>>
>>> Entries created are as follows:
>>> /local/domain/0/backend/pci/1/0
>>> vdev-N
>>> BDF = ""
>>> BAR-0-IPA = ""
>>> BAR-0-PA = ""
>>> BAR-0-SIZE = ""
>>> ...
>>> BAR-M-IPA = ""
>>> BAR-M-PA = ""
>>> BAR-M-SIZE = ""
>>>
>>> Note: If BAR M SIZE is 0, it is not a valid entry.
>>
>> How would you describe the ROM in xenstore?
>
> You mean the ROM BAR? BAR-ROM-* perhaps?
Right I mean the ROM BAR. I think it's should be spell out in the design
document.
Although I don't much care about the name.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-09-02 15:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 9:42 PCI Pass-through in Xen ARM: Draft 4 Manish Jaggi
2015-08-13 10:37 ` Julien Grall
2015-09-02 15:19 ` Ian Campbell
2015-09-02 15:40 ` Julien Grall [this message]
2015-08-13 15:29 ` Jan Beulich
2015-08-13 17:01 ` Ian Campbell
2015-08-14 9:26 ` Jan Beulich
2015-08-14 13:21 ` Stefano Stabellini
2015-08-14 13:58 ` Jan Beulich
2015-08-14 14:03 ` Stefano Stabellini
2015-08-14 14:34 ` Jan Beulich
2015-08-14 14:37 ` Stefano Stabellini
2015-08-14 14:45 ` Julien Grall
2015-08-14 15:15 ` Jan Beulich
2015-08-14 15:24 ` Stefano Stabellini
2015-09-02 14:45 ` Ian Campbell
2015-09-02 14:52 ` Jan Beulich
2015-09-02 15:07 ` Ian Campbell
2015-09-02 14:47 ` Ian Campbell
2015-08-14 15:38 ` Stefano Stabellini
2015-08-14 18:58 ` Jaggi, Manish
2015-08-16 23:59 ` Stefano Stabellini
2015-09-02 14:57 ` Ian Campbell
2015-09-02 15:06 ` Jan Beulich
2015-08-31 12:36 ` Manish Jaggi
2015-09-01 7:32 ` Jan Beulich
2015-09-02 12:08 ` Manish Jaggi
2015-09-02 12:59 ` Julien Grall
2015-09-02 13:46 ` Ian Campbell
2015-09-02 15:03 ` Ian Campbell
2015-09-02 15:03 ` Ian Campbell
2015-09-01 16:15 ` Stefano Stabellini
2015-09-10 1:12 ` Julien Grall
2015-09-15 18:58 ` Jaggi, Manish
2015-09-15 21:18 ` David Daney
2015-09-16 12:58 ` Julien Grall
2015-09-19 20:24 ` Manish Jaggi
2015-09-19 20:48 ` Julien Grall
2015-09-19 21:51 ` Daney, David
2015-09-21 10:17 ` Julien Grall
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=55E7187D.2090901@citrix.com \
--to=julien.grall@citrix.com \
--cc=Prasun.kapoor@cavium.com \
--cc=Vijaya.Kumar@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=mjaggi@caviumnetworks.com \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.