linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@hpe.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Steve Wahl <steve.wahl@hpe.com>,
	Mike Travis <mike.travis@hpe.com>,
	Dimitri Sivanich <dimitri.sivanich@hpe.com>,
	Russ Anderson <russ.anderson@hpe.com>,
	Robin Holt <robinmholt@gmail.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: 16-bit _SEG vs 8 bit PCIe Flit mode Segment
Date: Wed, 2 Nov 2022 10:33:25 -0500	[thread overview]
Message-ID: <20221102153325.GA221768@hpe.com> (raw)
In-Reply-To: <20221101144905.GA1258094@bhelgaas>

Bjorn,

Thanks for letting us know about this.

This is just to let you know that, while we are still investigating this,
our UV3 Broadwell era systems do use more than 8 bits for the segment #.

From lscpi on UV3:
  1007:3f:08.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 QPI Link 0 (rev 07)

Dimitri

On Tue, Nov 01, 2022 at 09:49:05AM -0500, Bjorn Helgaas wrote:
> ACPI r6.5, sec 6.5.6, currently says the low 16 bits of _SEG are the
> PCI Segment Group number.  PCIe r6.0, sec 2.2.1.2, added Flit mode
> with TLP headers that may contain an 8-bit Segment number.
> 
> ACPI currently says _SEG is purely a software thing and has no
> connection to any physical entities.  But this may get a little blurry
> when Segment numbers appear in TLPs.  For example, AER header logs
> will likely contain the Flit Segment, and we'll need to correlate that
> with the _SEG-derived identifiers Linux uses.
> 
> One possibility is to reduce the width of _SEG to 8 bits to match the
> Flit mode Segment and require them to be identical.
> 
> I'm trying to figure out whether that would break any existing
> systems.  I've heard rumors that large systems like SGI UV may use
> more than 8 bits of _SEG.  But I don't know any details.
> 
> Bjorn

      reply	other threads:[~2022-11-02 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 14:49 16-bit _SEG vs 8 bit PCIe Flit mode Segment Bjorn Helgaas
2022-11-02 15:33 ` Dimitri Sivanich [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=20221102153325.GA221768@hpe.com \
    --to=sivanich@hpe.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=helgaas@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mike.travis@hpe.com \
    --cc=rafael@kernel.org \
    --cc=robinmholt@gmail.com \
    --cc=russ.anderson@hpe.com \
    --cc=steve.wahl@hpe.com \
    /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).