From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
somlo@cmu.edu, xiaolong.ye@intel.com
Subject: Re: [Qemu-devel] [PATCH v7 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support
Date: Thu, 23 Nov 2017 07:19:03 +0200 [thread overview]
Message-ID: <20171123071842-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171120095519.15214-1-marcandre.lureau@redhat.com>
On Mon, Nov 20, 2017 at 10:55:14AM +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 upcoming
> qemu release (2.11).
Does not help. Still get crashes from ltp.
> v7:
> - add a patch to fix driver remove()
> - remove DMA operatiom timeout (qemu finishes sync today)
> - synchronize the DMA transfer before reading from CPU
> - removed kmalloc() use static allocation instead
> - drop some r-b tags
>
> v6:
> - change acpi_acquire_global_lock() error to return EINVAL
> (instead of EBUSY)
> - replace 0 as pointer argument for NULL
> - add Gabriel r-b/a-b tags
>
> v5:
> - resent to CC kdump people on the paddr_vmcoreinfo_note() export patch
>
> 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
>
> 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 driver remove
> 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 | 276 ++++++++++++++++++++++++++++++++++++-----
> kernel/crash_core.c | 1 +
> 2 files changed, 247 insertions(+), 30 deletions(-)
>
> --
> 2.15.0.277.ga3d2ad2c43
prev parent reply other threads:[~2017-11-23 5:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 9:55 [Qemu-devel] [PATCH v7 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support Marc-André Lureau
2017-11-20 9:55 ` [Qemu-devel] [PATCH v7 1/5] fw_cfg: fix driver remove Marc-André Lureau
2017-11-20 9:55 ` [Qemu-devel] [PATCH v7 2/5] fw_cfg: add DMA register Marc-André Lureau
2017-11-20 9:55 ` [Qemu-devel] [PATCH v7 3/5] fw_cfg: do DMA read operation Marc-André Lureau
2017-11-20 21:49 ` Michael S. Tsirkin
2017-11-21 11:17 ` Marc-André Lureau
2017-11-21 16:24 ` Michael S. Tsirkin
2017-11-20 9:55 ` [Qemu-devel] [PATCH v7 4/5] crash: export paddr_vmcoreinfo_note() Marc-André Lureau
2017-11-20 9:55 ` [Qemu-devel] [PATCH v7 5/5] fw_cfg: write vmcoreinfo details Marc-André Lureau
2017-11-23 5:19 ` Michael S. Tsirkin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171123071842-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).