From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: somlo@cmu.edu, xiaolong.ye@intel.com, qemu-devel@nongnu.org,
mst@redhat.com, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PATCH v8 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support
Date: Thu, 23 Nov 2017 15:02:01 +0100 [thread overview]
Message-ID: <20171123140206.3911-1-marcandre.lureau@redhat.com> (raw)
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).
v8:
- fix ltp again: bring back kmalloc() for DMA memory (see "What memory
is DMA'able?" limitations in Documentation/DMA-API-HOWTO.txt)
Interestingly, it didn't fail when the module was linked in..
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 | 283 ++++++++++++++++++++++++++++++++++++-----
kernel/crash_core.c | 1 +
2 files changed, 254 insertions(+), 30 deletions(-)
--
2.15.0.277.ga3d2ad2c43
next reply other threads:[~2017-11-23 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 14:02 Marc-André Lureau [this message]
2017-11-23 14:02 ` [Qemu-devel] [PATCH v8 1/5] fw_cfg: fix driver remove Marc-André Lureau
2017-11-23 14:02 ` [Qemu-devel] [PATCH v8 2/5] fw_cfg: add DMA register Marc-André Lureau
2017-11-23 14:02 ` [Qemu-devel] [PATCH v8 3/5] fw_cfg: do DMA read operation Marc-André Lureau
2017-12-01 15:14 ` Michael S. Tsirkin
2017-11-23 14:02 ` [Qemu-devel] [PATCH v8 4/5] crash: export paddr_vmcoreinfo_note() Marc-André Lureau
2017-11-23 14:36 ` Christoph Hellwig
2017-11-24 4:20 ` Michael S. Tsirkin
2017-11-23 14:02 ` [Qemu-devel] [PATCH v8 5/5] fw_cfg: write vmcoreinfo details Marc-André Lureau
2017-11-29 1:23 ` [Qemu-devel] [PATCH v8 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support Michael S. Tsirkin
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=20171123140206.3911-1-marcandre.lureau@redhat.com \
--to=marcandre.lureau@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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).