qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Gabriel L. Somlo" <somlo@cmu.edu>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: linux-kernel@vger.kernel.org, somlo@cmu.edu,
	qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support
Date: Sun, 12 Nov 2017 07:40:03 -0500	[thread overview]
Message-ID: <20171112124003.GA19857@hedwig.ini.cmu.edu> (raw)
In-Reply-To: <20171031151938.14982-1-marcandre.lureau@redhat.com>

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
> 

      parent reply	other threads:[~2017-11-12 12:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 15:19 [Qemu-devel] [PATCH v4 0/5] fw_cfg: add DMA operations & etc/vmcoreinfo support Marc-André Lureau
2017-10-31 15:19 ` [Qemu-devel] [PATCH v4 1/5] fw_cfg: fix the command line module name Marc-André Lureau
2017-11-12 12:40   ` Gabriel L. Somlo
2017-10-31 15:19 ` [Qemu-devel] [PATCH v4 2/5] fw_cfg: add DMA register Marc-André Lureau
2017-11-12 12:41   ` Gabriel L. Somlo
2017-10-31 15:19 ` [Qemu-devel] [PATCH v4 3/5] fw_cfg: do DMA read operation Marc-André Lureau
2017-11-12 12:42   ` Gabriel L. Somlo
2017-11-12 14:36     ` Marc-André Lureau
2017-11-12 19:21       ` Gabriel L. Somlo
2017-10-31 15:19 ` [Qemu-devel] [PATCH v4 4/5] crash: export paddr_vmcoreinfo_note() Marc-André Lureau
2017-11-12 12:42   ` Gabriel L. Somlo
2017-10-31 15:19 ` [Qemu-devel] [PATCH v4 5/5] fw_cfg: write vmcoreinfo details Marc-André Lureau
2017-11-12 12:43   ` Gabriel L. Somlo
2017-11-12 12:40 ` Gabriel L. Somlo [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=20171112124003.GA19857@hedwig.ini.cmu.edu \
    --to=somlo@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).