From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: linux-kernel@vger.kernel.org, slp@redhat.com, bhe@redhat.com,
somlo@cmu.edu, xiaolong.ye@intel.com
Subject: Re: [PATCH v11 0/4] fw_cfg: add DMA operations & etc/vmcoreinfo support
Date: Fri, 2 Feb 2018 04:50:42 +0200 [thread overview]
Message-ID: <20180202044841-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180201130300.9962-1-marcandre.lureau@redhat.com>
On Thu, Feb 01, 2018 at 02:02:56PM +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 (since qemu 2.11).
At this point you need to scope this down significantly. I'll give the
vmcore one more chance in this release if you test the hell out of it with 32 and 64 bit
guests and repost tomorrow with just the vmcore enabled and that ASAP,
and without kmalloc on crash which is problematic by itself.
> v11:
> - add #include <linux/crash_core.h> in last patch,
> fixing kbuild .config test
>
> Marc-André Lureau (4):
> 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 | 268 ++++++++++++++++++++++++++++++++++++-----
> kernel/crash_core.c | 1 +
> 2 files changed, 237 insertions(+), 32 deletions(-)
>
> --
> 2.16.0.rc1.1.gef27df75a1
prev parent reply other threads:[~2018-02-02 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 13:02 [PATCH v11 0/4] fw_cfg: add DMA operations & etc/vmcoreinfo support Marc-André Lureau
2018-02-01 13:02 ` [PATCH v11 1/4] fw_cfg: add DMA register Marc-André Lureau
2018-02-01 13:02 ` [PATCH v11 2/4] fw_cfg: do DMA read operation Marc-André Lureau
2018-02-02 2:47 ` Michael S. Tsirkin
2018-02-01 13:02 ` [PATCH v11 3/4] crash: export paddr_vmcoreinfo_note() Marc-André Lureau
2018-02-01 13:03 ` [PATCH v11 4/4] fw_cfg: write vmcoreinfo details Marc-André Lureau
2018-02-02 2:44 ` Michael S. Tsirkin
2018-02-02 9:43 ` Marc-Andre Lureau
2018-02-02 2:50 ` 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=20180202044841-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=slp@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.