From: Jiandi An <anjiandi@codeaurora.org>
To: xen-devel@lists.xen.org
Cc: Julien Grall <julien.grall@arm.com>,
sstabellini@kernel.org, anjiandi@codeaurora.org,
shankerd@codeaurora.org
Subject: Xen: ARM: Support for mapping ECAM PCIe Config Space Specified In Static ACPI Table
Date: Wed, 14 Dec 2016 02:00:15 -0600 [thread overview]
Message-ID: <5850FC0F.4070307@codeaurora.org> (raw)
Hi Guys,
Xen currently doesn't map ECAM space specified in static ACPI table. Seeking opinion on how this should be handled properly. Each root complex ECAM region takes up 64K 4K pages (256MB). For some platforms there might be multiple root complexes. Is the plan to map all at once? Julien has mentioned support for mapping ECAM may come when support for PCI passthrough is added, is that right? What mechanism will it be? Will Xen or dom0 be the one that parses the staic ACPI tables and map the ECAM space?
Thanks.
--
Jiandi An
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-12-14 8:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 8:00 Jiandi An [this message]
2016-12-16 14:49 ` Xen: ARM: Support for mapping ECAM PCIe Config Space Specified In Static ACPI Table Julien Grall
2016-12-19 10:37 ` Julien Grall
2016-12-19 12:20 ` Jaggi, Manish
2016-12-19 13:11 ` Julien Grall
2016-12-20 6:31 ` Jiandi An
2016-12-20 11:38 ` Julien Grall
2016-12-20 22:40 ` Stefano Stabellini
2016-12-19 23:54 ` Stefano Stabellini
2016-12-20 12:02 ` Julien Grall
2016-12-20 22:33 ` Stefano Stabellini
2016-12-28 18:22 ` Julien Grall
2017-01-03 9:10 ` Jan Beulich
2017-01-03 19:27 ` Stefano Stabellini
2017-01-16 14:05 ` Julien Grall
2017-01-16 19:28 ` Stefano Stabellini
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=5850FC0F.4070307@codeaurora.org \
--to=anjiandi@codeaurora.org \
--cc=julien.grall@arm.com \
--cc=shankerd@codeaurora.org \
--cc=sstabellini@kernel.org \
--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).