Message-ID: <20190809130911.bkflwxbeslhmdxu5@rric.localdomain>
Date:   Fri, 9 Aug 2019 13:09:18 +0000
From:   Robert Richter <rrichter@...vell.com>
To:     James Morse <james.morse@....com>
CC:     Borislav Petkov <bp@...en8.de>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 15/24] EDAC, ghes: Extract numa node information for
 each dimm

Hi James,

On 02.08.19 18:05:07, James Morse wrote:
> On 24/06/2019 16:09, Robert Richter wrote:
> > In a later patch we want to have one mc device per node. This patch
> > extracts the numa node information for each dimm. This is done by
> > collecting the physical address ranges from the DMI table (Memory
> > Array Mapped Address - Type 19 of SMBIOS spec). The node information
> > for a physical address is already know to a numa aware system (e.g. by
> > using the ACPI _PXM method or the ACPI SRAT table), so based on the PA
> > we can assign the node id to the dimms.
> 
> I really don't like the way this depends on the rest of the kernel's NUMA support.
> mm's policies around the placement of data change with these settings, that shouldn't
> matter here. Reporting physical errors shouldn't be influenced by mm's placement policy.
> 
> pfn_valid() is a sore subject on arm64, it will return false for random pages that the
> firmware is using, or wrote data to with unusual memory attributes. Depending on it makes
> this code fragile...
> 
> 
> > A fallback that disables numa is implemented in case the node
> > information is inconsistent.
> 
> ... which is why you need a fallback.

I don't agree here. pfn_valid() and page_to_nid() are reliable used in
numa systems to identify the node of a physical address. Same is used
here. If firmware does not provide consistent topology data, numa
would not work either and a non-numa fallback is in place. You say
this code is fragile, which would mean numa code is fragile too, but
it isn't.

Node information and the 1:1 mapping between node and an edac mc
device are essential for error handling. All other drivers have one mc
device per node. If you don't follow this topology layout you will
have significant differences in the ghes error handling compared to
other drivers. But this driver (and arm64 systems) should provide a
similar functionality.

> All this makes it difficult to explain why this things view of memory is as it is.
> Making the RAS/edac code unpredictable like this is a hard sell.
> 
> You need to squint through Kconfig, SRAT and the UEFI memory map.
> (due to pfn_valid(): the behaviour here can change over a reboot)
> 
> 
> Can we 'just' use the type-16 handle to group the DIMMs?
> 
> As an illustration:
> http://www.linux-arm.org/git?p=linux-jm.git;a=shortlog;h=refs/heads/edac_ghes_2level_dimms/v0

I have looked into your code. You group all dimms under md0 and have
an additional layer for the phys mem arrays. This ignores the cper
layers (node, card, module). The way you add the layer may cause the
creation of dimm entries under md0 that even do not exist in the dmi
table. But dimms and their labels created by edac should reflect the
system as described in the dmi table.

My code creates one mdX device per node and groups the dimms under
them according to the dmi table. For this it further parses the
physical address range of the memory arrays and extracts the numa node
from it. I don't see what is wrong with that. The only added
dependency is the node lookup which is used somewhere else in the
kernel anyway on numa systems. But it provides a much better grouping
of hardware errors, which is then similar to other drivers.

I think your concern is more about code complexity, so I will go
through my code and keep it as simple as possible.

> This reflects the SMBIOS tables on my NUMA desktop, and doesn't depend on any of the
> above. I'd be interested to know what is missing from this approach.
> 
> (which numa node? I don't think we need to know the mapping of mcX<->nid up front. We can
> find it from the faulting physical address when we get an error report).
> 
> 
> N.B, your mail is still arriving base64 encoded. It looks like this:
> https://lore.kernel.org/linux-edac/20190624150758.6695-16-rrichter@marvell.com/raw
> 
> Lei Wang found:
> > Ah I found if without explicit "--transfer-encoding=7bit" when do "git
> > send-mail", my ubuntu box sent out base64 by default.
> 
> (but his mail didn't get archived for some reason)

Thanks for the note, I will check the encoding.

Thank you for review.

-Robert

Powered by blists - more mailing lists