From: Sinan Kaya <okaya@codeaurora.org>
To: Linux PCI <linux-pci@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: RFC on MCFG Table Support
Date: Tue, 17 Apr 2018 12:18:22 -0400 [thread overview]
Message-ID: <bd3f4d3a-f641-7385-4ce2-d62a28bc9cd3@codeaurora.org> (raw)
Hi,
QDT is working with PCI-SIG to revisit some of the spec language ambiguity
on the definition of PCI Segment Group in PCI FW Specification.
PCI spec is currently requiring a single entry per segment in the MCFG table
with a contiguous 256MB range.
Based on our research, this rule is being violated in the industry for existing
platforms due to the different ways spec is interpreted.
We are trying to remove this restriction in the spec and have multiple entries
per segment as long as <segment, bus start number, bus end number> tuple is
unique.
AFAIS, generic ACPI Linux driver already supports this via pci_mcfg_lookup().
I also did a prototype and observed that I can enumerate two root ports without
any issues.
I wanted to seek opinion on whether this is a valid assumption and if I'm missing
something.
Sinan
--
Sinan Kaya
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.
next reply other threads:[~2018-04-17 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 16:18 Sinan Kaya [this message]
2018-04-17 20:04 ` RFC on MCFG Table Support Bjorn Helgaas
2018-04-17 20:09 ` Sinan Kaya
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=bd3f4d3a-f641-7385-4ce2-d62a28bc9cd3@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.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).