From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: RFC on MCFG Table Support
Date: Tue, 17 Apr 2018 16:09:24 -0400 [thread overview]
Message-ID: <22609a39-d701-9b36-f99f-0334aee88c6a@codeaurora.org> (raw)
In-Reply-To: <20180417200441.GL28657@bhelgaas-glaptop.roam.corp.google.com>
On 4/17/2018 4:04 PM, Bjorn Helgaas wrote:
>> 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.
> I hope you mean the <start, end> tuples are more than just unique;
> they shouldn't overlap, i.e., a given <segment, bus number> should
> match at most one MCFG entry.
Agreed, I'm talking about no overlap.
--
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.
prev parent reply other threads:[~2018-04-17 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 16:18 RFC on MCFG Table Support Sinan Kaya
2018-04-17 20:04 ` Bjorn Helgaas
2018-04-17 20:09 ` Sinan Kaya [this message]
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=22609a39-d701-9b36-f99f-0334aee88c6a@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=helgaas@kernel.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).