Re: [PATCH 5/5] hw/mem/cxl_type3: Refactor CDAT sub-table entry initialization into a function

2022-10-14 Thread Jonathan Cameron via
On Thu, 13 Oct 2022 15:40:47 -0400 Gregory Price wrote: > > > /* For now, no memory side cache, plausiblish numbers */ > > > -*dslbis_nonvolatile1 = (CDATDslbis) { > > > +*dslbis1 = (CDATDslbis) { > > > .header = { > > > .type = CDAT_TYPE_DSLBIS, > > > -

Re: [PATCH 5/5] hw/mem/cxl_type3: Refactor CDAT sub-table entry initialization into a function

2022-10-13 Thread Gregory Price
> > /* For now, no memory side cache, plausiblish numbers */ > > -*dslbis_nonvolatile1 = (CDATDslbis) { > > +*dslbis1 = (CDATDslbis) { > > .header = { > > .type = CDAT_TYPE_DSLBIS, > > -.length = sizeof(*dslbis_nonvolatile1), > > +.length

Re: [PATCH 5/5] hw/mem/cxl_type3: Refactor CDAT sub-table entry initialization into a function

2022-10-13 Thread Jonathan Cameron via
On Wed, 12 Oct 2022 14:21:20 -0400 Gregory Price wrote: > The CDAT can contain multiple entries for multiple memory regions, this > will allow us to re-use the initialization code when volatile memory > region support is added. > > Signed-off-by: Gregory Price I'm in two minds about this...

[PATCH 5/5] hw/mem/cxl_type3: Refactor CDAT sub-table entry initialization into a function

2022-10-12 Thread Gregory Price
The CDAT can contain multiple entries for multiple memory regions, this will allow us to re-use the initialization code when volatile memory region support is added. Signed-off-by: Gregory Price --- hw/mem/cxl_type3.c | 137 - 1 file changed, 72