On Tue, Feb 23, 2016 at 04:12:02PM -0600, Rob Herring wrote: > On Tue, Feb 23, 2016 at 11:58:05AM +0000, Mark Rutland wrote: > > Hi, > > > > On Mon, Feb 22, 2016 at 05:58:19PM -0800, David Daney wrote: > > > From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> > > > > > > There are two problems with the UEFI stub DT memory node removal > > > routine: > > > - it deletes nodes as it traverses the tree, which happens to work > > > but is not supported, as deletion invalidates the node iterator; > > > - deleting memory nodes entirely may discard annotations in the form > > > of additional properties on the nodes. > > > > > > Since the discovery of DT memory nodes occurs strictly before the > > > UEFI init sequence, we can simply clear the memblock memory table > > > before parsing the UEFI memory map. This way, it is no longer > > > necessary to remove the nodes, so we can remove that logic from the > > > stub as well. > > > > This is a little bit scary, but I guess this works. > > The way it is worded/implemented is, I agree. But if we simply say both > can be present and the kernel will default to UEFI memory map, that > seems sufficient to me. > > > My only concern is that when we get kexec, a subsequent kernel must also > > have EFI memory map support, or things go bad for the next EFI-aware > > kernel after that (as things like the runtime services may have been > > corrupted by the kernel in the middle). It's difficult to fix the > > general case later. > > > > A different option would be to support status="disabled" for the memory > > nodes, and ignore these in early_init_dt_scan_memory. That way a kernel > > cannot use memory without first having parsed the EFI memory map, and we > > can still get NUMA info from the disabled nodes. > > That would be a bit strange that the node is disabled, but still used. I agree this would be strange, and not necessarily a precedent we'd want to see copied elsewhere. Per ePAPR, a "disabled" node can be enabled in a binding-specific manner, so having the presence of a UEFI memory map "enable" the NUMA information would appear to be permitted. > What if DT and UEFI tables are out of sync somehow? RAM is multiple > mapped and different addresses were picked for example. That applies regardless of the status of the memory nodes. My suggestion was only that we acquired the NUMA node information, and added this node information (and not any additional extent of memory) to the UEFI memory map. This is precisely what we do with Ard's code, with the exception that in the absence of a UEFI memory map the kernel would know it was not permitted to access memory. Mark. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
