From: Laszlo Ersek <lersek@redhat.com>
To: Qiao Nuohan <qiaonuohan@cn.fujitsu.com>
Cc: stefanha@gmail.com, Amos <akong@redhat.com>,
qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/9] Make 'dump-guest-memory' dump in kdump-compressed format
Date: Wed, 31 Jul 2013 14:23:08 +0200 [thread overview]
Message-ID: <51F901AC.40909@redhat.com> (raw)
In-Reply-To: <51F8D842.3040607@cn.fujitsu.com>
Hi Qiao,
On 07/31/13 11:26, Qiao Nuohan wrote:
> Hello Luiz and Amos,
>
> My patches are waiting for introspection. But now I cannot quite catch
> the situation of introspection, so I hope to get some information about
> current state from you. It will be very appreciated.
I wasn't aware that you've been working on dump changes.
I'm afraid this series of yours, and my series
[Qemu-devel] [PATCH 0/4] dump-guest-memory: correct the vmcores
http://lists.nongnu.org/archive/html/qemu-devel/2013-07/msg05469.html
are going to conflict violently.
Since my series is a bugfix for existing, non-compressed functionality
(--> vmcores dumped for 3.5G+ guests are corrupt), *and* you look like a
vmcore/dump expert, could you please give it a look? :)
Normally, your series *should* take priority, because it's been on the
list for much longer. However considering the 1.6 hard freeze, my
series, being a bugfix, might go in earlier. Do you think you could
rebase your work on mine (if it is accepted, that is)?
Apologies for the mess...
Thanks
Laszlo
next prev parent reply other threads:[~2013-07-31 12:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 7:30 [Qemu-devel] [PATCH v5 0/9] Make 'dump-guest-memory' dump in kdump-compressed format Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 1/9] dump: Add argument to write_elfxx_notes Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 2/9] dump: Add API to write header of flatten format Qiao Nuohan
2013-07-16 2:06 ` Stefan Hajnoczi
2013-07-16 3:50 ` Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 3/9] dump: Add API to write vmcore Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 4/9] dump: Add API to write elf notes to buffer Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 5/9] dump: add API to write dump header Qiao Nuohan
2013-07-16 2:18 ` Stefan Hajnoczi
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 6/9] dump: Add API to write dump_bitmap Qiao Nuohan
2013-07-16 2:25 ` Stefan Hajnoczi
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 7/9] dump: Add APIs to operate DataCache Qiao Nuohan
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 8/9] dump: Add API to write dump pages Qiao Nuohan
2013-07-16 2:43 ` Stefan Hajnoczi
2013-07-16 3:40 ` Qiao Nuohan
2013-07-16 16:28 ` Eric Blake
2013-07-09 7:30 ` [Qemu-devel] [PATCH v5 9/9] dump: Make kdump-compressed format available for 'dump-guest-memory' Qiao Nuohan
2013-07-09 7:36 ` [Qemu-devel] [PATCH v5 0/9] Make 'dump-guest-memory' dump in kdump-compressed format Qiao Nuohan
2013-07-15 9:56 ` Qiao Nuohan
2013-07-16 2:45 ` Stefan Hajnoczi
2013-07-31 9:26 ` Qiao Nuohan
2013-07-31 12:23 ` Laszlo Ersek [this message]
2013-07-31 13:10 ` Luiz Capitulino
2013-08-02 3:25 ` Qiao Nuohan
2013-08-02 3:41 ` Amos Kong
2013-08-02 3:43 ` Qiao Nuohan
2013-08-02 3:37 ` Qiao Nuohan
2013-12-13 2:07 ` Qiao Nuohan
2013-12-13 2:25 ` Eric Blake
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=51F901AC.40909@redhat.com \
--to=lersek@redhat.com \
--cc=akong@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaonuohan@cn.fujitsu.com \
--cc=stefanha@gmail.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).