Message ID | 20171123140206.3911-5-marcandre.lureau@redhat.com |
---|---|
State | New |
Headers | show |
Series | fw_cfg: add DMA operations & etc/vmcoreinfo support | expand |
On Thu, Nov 23, 2017 at 03:02:05PM +0100, Marc-André Lureau wrote: > The following patch is going to use the symbol from the fw_cfg module, > to call the function and write the note location details in the > vmcoreinfo entry, so qemu can produce dumps with the vmcoreinfo note. Sounds like fw_cfg should be moved to be built in only instead of exporting such a symbol address.
On Thu, Nov 23, 2017 at 06:36:57AM -0800, Christoph Hellwig wrote: > On Thu, Nov 23, 2017 at 03:02:05PM +0100, Marc-André Lureau wrote: > > The following patch is going to use the symbol from the fw_cfg module, > > to call the function and write the note location details in the > > vmcoreinfo entry, so qemu can produce dumps with the vmcoreinfo note. > > Sounds like fw_cfg should be moved to be built in only instead of > exporting such a symbol address. Point is, all fw cfg does is export it on to the hypervisor, so it will have to be supported forever. If it's safe to export it to the hypervisor then for sure it's also safe to export it to modules.
diff --git a/kernel/crash_core.c b/kernel/crash_core.c index b3663896278e..2394f0501c65 100644 --- a/kernel/crash_core.c +++ b/kernel/crash_core.c @@ -376,6 +376,7 @@ phys_addr_t __weak paddr_vmcoreinfo_note(void) { return __pa(vmcoreinfo_note); } +EXPORT_SYMBOL(paddr_vmcoreinfo_note); static int __init crash_save_vmcoreinfo_init(void) {