On Mon, Jan 09, 2023 at 04:30:28PM -0800, matthew.gerlach@xxxxxxxxxxxxxxx wrote: > From: Matthew Gerlach <matthew.gerlach@xxxxxxxxxxxxxxx> > > Version 1 of the Device Feature Header (DFH) definition adds > functionality to the Device Feature List (DFL) bus. > > A DFHv1 header may have one or more parameter blocks that > further describes the HW to SW. Add support to the DFL bus > to parse the MSI-X parameter. > > The location of a feature's register set is explicitly > described in DFHv1 and can be relative to the base of the DFHv1 > or an absolute address. Parse the location and pass the information > to DFL driver. ... > v10: change dfh_find_param to return size of parameter data in bytes The problem that might occur with this approach is byte ordering. When we have u64 items, we know that they all are placed in CPU ordering by the bottom layer. What's the contract now? Can it be a problematic? Please double check this (always keep in mind BE32 as most interesting case for u64/unsigned long representation and other possible byte ordering outcomes). -- With Best Regards, Andy Shevchenko
