linux-kernel - 16-bit _SEG vs 8 bit PCIe Flit mode Segment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221101144905.GA1258094@bhelgaas>
Date:   Tue, 1 Nov 2022 09:49:05 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Steve Wahl <steve.wahl@....com>
Cc:     Mike Travis <mike.travis@....com>,
        Dimitri Sivanich <dimitri.sivanich@....com>,
        Russ Anderson <russ.anderson@....com>,
        Robin Holt <robinmholt@...il.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: 16-bit _SEG vs 8 bit PCIe Flit mode Segment

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