[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171112124003.GA19857@hedwig.ini.cmu.edu>
Date: Sun, 12 Nov 2017 07:40:03 -0500
From: "Gabriel L. Somlo" <somlo@....edu>
To: Marc-André Lureau <marcandre.lureau@...hat.com>
Cc: linux-kernel@...r.kernel.org, somlo@....edu, qemu-devel@...gnu.org,
mst@...hat.com
Subject: Re: [PATCH v4 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo
support
On Tue, Oct 31, 2017 at 04:19:33PM +0100, Marc-André Lureau wrote:
> Hi,
>
> This series adds DMA operations support to the qemu fw_cfg kernel
> module and populates "etc/vmcoreinfo" with vmcoreinfo location
> details.
>
> Note: the support for this entry handling has been merged for next
> qemu release (2.11)
>
> v4:
> - export paddr_vmcoreinfo_note() to fix fw_cfg.ko build
> - fix build with !CONFIG_CRASH_CORE
> - replace the unbounded yield() loop with a usleep_range() loop and a
> 200ms timeout
> - do not write vmcoreinfo entry when running the kdump kernel (D. Hatayama)
> - drop the experimental sysfs write support patch from this series
Tested it on x86_64, appears to work fine.
I have a couple of silly questions re. 3/5 and 5/5. Lost the v5 emails
with the vmcore folks cc-ed, but my questions are unrelated to vmcore
anyway :)
Thanks,
--Gabriel
>
> v3: (thanks kbuild)
> - add "fw_cfg: fix the command line module name" patch
> - fix build of "fw_cfg: add DMA register" with CONFIG_FW_CFG_SYSFS_CMDLINE=y
> - fix 'Wshift-count-overflow'
>
> v2:
> - use platform device for dma mapping
> - add etc/vmcoreinfo patch
> - some code cleanups
>
> Marc-André Lureau (5):
> fw_cfg: fix the command line module name
> fw_cfg: add DMA register
> fw_cfg: do DMA read operation
> crash: export paddr_vmcoreinfo_note()
> fw_cfg: write vmcoreinfo details
>
> drivers/firmware/qemu_fw_cfg.c | 292 +++++++++++++++++++++++++++++++++++++----
> kernel/crash_core.c | 1 +
> 2 files changed, 264 insertions(+), 29 deletions(-)
>
> --
> 2.15.0.rc0.40.gaefcc5f6f
>
Powered by blists - more mailing lists