BugLink: https://bugs.launchpad.net/bugs/2028158
By default this is enabled, but it is causing an issue reconfiguring device dax memory, thus
it is being disabled.
Signed-off-by: Michael Reed <email address hidden>
So called "soft-reserved" memory is an EFI conventional memory range
with the EFI_MEMORY_SP attribute set. That attribute indicates that the
memory is not part of the platform general purpose memory pool and may
want some consideration from the system administrator about whether to
keep that memory set aside for dedicated access through device-dax (map
a device file), or assigned to the page allocator as another general
purpose memory node target.
Absent an ACPI HMAT table the default device-dax registration creates
coarse grained devices that are delineated by EFI Memory Map entries.
With the HMAT the devices are delineated by the finer grained ranges
associated with the proximity domain of the memory target. I.e. the HMAT
describes the properties of performance differentiated memory and each
unique performance description results in a unique target proximity
domain where each memory proximity domain has an associated SRAT entry
that delineates the address range.
The intent was that SRAT-defined device-dax instances are registered
first. Then any left-over address range with the EFI_MEMORY_SP
attribute, but not covered by the SRAT, would have a coarse grained
device-dax instance established. However, the scheme to detect what
ranges are left to be assigned to a device was buggy and resulted in
multiple overlapping device-dax instances. Fix this by using explicit
tracking for which ranges have been handled.
Now, this new approach may leave memory stranded in the presence of
broken platform firmware that fails to fully describe all EFI_MEMORY_SP
ranges in the HMAT. That requires a deeper fix if it becomes a problem
in practice.
Reported-by: "Tallam Mahendra Kumar" <email address hidden>
Reported-by: Mustafa Hajeer <email address hidden>
Debugged-by: Vishal Verma <email address hidden>
Tested-by: Vishal Verma <email address hidden>
Link: https://lore<email address hidden>
Signed-off-by: Dan Williams <email address hidden>
(backported from commit 472faf72b33d80aa8e7a99c9410c1a23d3bf0cd8)
[Michael Reed - Simple adjustment for location of patch]
Signed-off-by: Michael Reed <email address hidden>
That option will disable AVX on systems where microcode mitigation has not
been provided. Though it can be flipeed by a boot option, it has been shown
to break some versions of gnutls, which are used by apt or git when dealing
with https.
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Roxana Nicolescu <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>
UBUNTU: [Config] Record version updates in binutils
GCC and pahole were updated to newer versions. Reflect this in the
annotation file. Also one option gets relocated when generating the
annotation file again. Commit the new location as well.
Ignore: yes
Signed-off-by: Stefan Bader <email address hidden>
