search for: firmware_map_add_early

...rks it as System RAM vs Soft Reserved. The 2008 patch > >>> simply does not consider that case. I'm not sure strict textualism > >>> works for coding decisions. > >> > >> I am no expert on that matter (esp EFI). But looking at the users of > >> firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c > >> . So the single source of /sys/firmware/memmap is (besides hotplug) e820. > >> > >> "'e820_table_firmware': the original firmware version passed to us by > >> the bootloader - not modified by the k...

...ap marked it as conventional RAM, but the kernel > optionally marks it as System RAM vs Soft Reserved. The 2008 patch > simply does not consider that case. I'm not sure strict textualism > works for coding decisions. I am no expert on that matter (esp EFI). But looking at the users of firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c . So the single source of /sys/firmware/memmap is (besides hotplug) e820. "'e820_table_firmware': the original firmware version passed to us by the bootloader - not modified by the kernel. ... inform the user about the firmware's not...

...ap marked it as conventional RAM, but the kernel > optionally marks it as System RAM vs Soft Reserved. The 2008 patch > simply does not consider that case. I'm not sure strict textualism > works for coding decisions. I am no expert on that matter (esp EFI). But looking at the users of firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c . So the single source of /sys/firmware/memmap is (besides hotplug) e820. "'e820_table_firmware': the original firmware version passed to us by the bootloader - not modified by the kernel. ... inform the user about the firmware's not...

...gt;>> optionally marks it as System RAM vs Soft Reserved. The 2008 patch >>> simply does not consider that case. I'm not sure strict textualism >>> works for coding decisions. >> >> I am no expert on that matter (esp EFI). But looking at the users of >> firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c >> . So the single source of /sys/firmware/memmap is (besides hotplug) e820. >> >> "'e820_table_firmware': the original firmware version passed to us by >> the bootloader - not modified by the kernel. ... inform th...

...gt;>> optionally marks it as System RAM vs Soft Reserved. The 2008 patch >>> simply does not consider that case. I'm not sure strict textualism >>> works for coding decisions. >> >> I am no expert on that matter (esp EFI). But looking at the users of >> firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c >> . So the single source of /sys/firmware/memmap is (besides hotplug) e820. >> >> "'e820_table_firmware': the original firmware version passed to us by >> the bootloader - not modified by the kernel. ... inform th...

...RAM, but the kernel > > optionally marks it as System RAM vs Soft Reserved. The 2008 patch > > simply does not consider that case. I'm not sure strict textualism > > works for coding decisions. > > I am no expert on that matter (esp EFI). But looking at the users of > firmware_map_add_early(), the single user is in arch/x86/kernel/e820.c > . So the single source of /sys/firmware/memmap is (besides hotplug) e820. > > "'e820_table_firmware': the original firmware version passed to us by > the bootloader - not modified by the kernel. ... inform the user about &gt...

On 01.05.20 20:03, Dan Williams wrote: > On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 19:45, David Hildenbrand wrote: >>> On 01.05.20 19:39, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On 01.05.20

On 01.05.20 20:03, Dan Williams wrote: > On Fri, May 1, 2020 at 10:51 AM David Hildenbrand <david at redhat.com> wrote: >> >> On 01.05.20 19:45, David Hildenbrand wrote: >>> On 01.05.20 19:39, Dan Williams wrote: >>>> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand <david at redhat.com> wrote: >>>>> >>>>> On 01.05.20

...be+0x5e/0x130 [ 19.256561] driver_probe_device+0x5c2/0x770 [ 19.256561] __driver_attach+0x14c/0x1d0 [ 19.256561] ? driver_probe_device+0x770/0x770 [ 19.256561] bus_for_each_dev+0xa7/0xf0 [ 19.256561] driver_attach+0x21/0x30 [ 19.256561] bus_add_driver+0x318/0x420 [ 19.256561] ? firmware_map_add_early+0x84/0x84 [ 19.256561] driver_register+0xa7/0x190 [ 19.256561] ? firmware_map_add_early+0x84/0x84 [ 19.256561] __platform_driver_register+0x39/0x50 [ 19.256561] fw_cfg_sysfs_init+0x4e/0x8e [ 19.256561] ? firmware_map_add_early+0x84/0x84 [ 19.256561] do_one_initcall+0x53/0x285 [...