Re: [PATCH kernel 1/9] pci/tsm: Add TDISP report blob and helpers to parse it

[dan.j.williams]

Alexey Kardashevskiy wrote:
[..]
> > Does the kernel have any use for the footer besides conveying it to
> > userspace?
> 
> PCIe says:
> 
> Example of such device specific information include:
> • A network device may include receive-side scaling (RSS) related information such as the RSS hash and
> mappings to the virtual station interface (VSI) queues, etc.
> • A NVMe device may include information about the associated name spaces, mapping of name space to
> command queue-pair mappings, etc.
> • Accelerators may report capabilities such as algorithms supported, queue depths, etc
> 
> 
> Sounds to me like something the device driver would be interested in.

That is not the concern. The concern is how does Linux maintain a
convention around these use case so that common semantics converge on a
common implementation expectations.

> >> imho easier on eyes. I can live with either if the majority votes for it. Thanks.
> > 
> > Aneesh also already has 'structs+bitmask', I will switch to that.
> 
> oh I just found it, more or less my version :) I can add pci_tdisp_ prefixes, should I? Thanks,

I have a patch brewing that moves interface report consumption into
encrypted resource population for ioremap() to consider. I will send
that out shortly.