On Mon, Aug 13, 2018 at 09:07:13AM +0200, Igor Mammedov wrote:
> On Fri, 10 Aug 2018 15:28:35 -0300
> Eduardo Habkost wrote:
>
> > On Fri, Aug 10, 2018 at 06:01:06PM +0200, Igor Mammedov wrote:
> > > On Fri, 10 Aug 2018 16:06:57 +0200
> > > Igor Mammedov wrote:
> > >
> > > > Commit 848a1cc1e8
On Fri, 10 Aug 2018 15:28:35 -0300
Eduardo Habkost wrote:
> On Fri, Aug 10, 2018 at 06:01:06PM +0200, Igor Mammedov wrote:
> > On Fri, 10 Aug 2018 16:06:57 +0200
> > Igor Mammedov wrote:
> >
> > > Commit 848a1cc1e8b04 while introducing SRAT entries for DIMM and NVDIMM
> > > also introduced fa
On Fri, Aug 10, 2018 at 06:01:06PM +0200, Igor Mammedov wrote:
> On Fri, 10 Aug 2018 16:06:57 +0200
> Igor Mammedov wrote:
>
> > Commit 848a1cc1e8b04 while introducing SRAT entries for DIMM and NVDIMM
> > also introduced fake entries for gaps between memory devices, assuming
> > that we need all
On Fri, 10 Aug 2018 16:06:57 +0200
Igor Mammedov wrote:
> Commit 848a1cc1e8b04 while introducing SRAT entries for DIMM and NVDIMM
> also introduced fake entries for gaps between memory devices, assuming
> that we need all possible range covered with SRAT entries.
> And it did it wrong since gap w
Commit 848a1cc1e8b04 while introducing SRAT entries for DIMM and NVDIMM
also introduced fake entries for gaps between memory devices, assuming
that we need all possible range covered with SRAT entries.
And it did it wrong since gap would overlap with preceeding entry.
Reproduced with following CLI:
