From: Peter Xu <peterx@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Eric Blake" <eblake@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
qemu-devel@nongnu.org, "Wen Congyang" <wency@cn.fujitsu.com>,
anderson@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/4] dump: add DumpInfo structure
Date: Tue, 6 Jun 2017 10:11:56 +0800 [thread overview]
Message-ID: <20170606021156.GL4056@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170605072438.qvxosyib2vpwl3a7@kamzik.brq.redhat.com>
On Mon, Jun 05, 2017 at 09:24:38AM +0200, Andrew Jones wrote:
> On Fri, Jun 02, 2017 at 09:46:35AM +0000, Marc-André Lureau wrote:
> > Hi
> >
> > On Thu, Jun 1, 2017 at 10:19 PM Eric Blake <eblake@redhat.com> wrote:
> >
> > > On 06/01/2017 01:06 PM, Laszlo Ersek wrote:
> > > > On 06/01/17 15:03, Marc-André Lureau wrote:
> > > >> One way or another, the guest could communicate various dump info (via
> > > >> guest agent or vmcoreinfo device) and populate that structure. It can
> > > >> then be used to augment the dump with various details, as done in the
> > > >> following patch.
> > > >>
> > > >> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> > > >> ---
> > > >> include/sysemu/dump-info.h | 18 ++++++++++++++++++
> > > >> dump.c | 3 +++
> > > >> 2 files changed, 21 insertions(+)
> > > >> create mode 100644 include/sysemu/dump-info.h
> > > >>
> > > >> diff --git a/include/sysemu/dump-info.h b/include/sysemu/dump-info.h
> > > >> new file mode 100644
> > > >> index 0000000000..d2378e15e2
> > > >> --- /dev/null
> > > >> +++ b/include/sysemu/dump-info.h
> > > >> @@ -0,0 +1,18 @@
> > > >> +#ifndef DUMP_INFO_H
> > > >> +#define DUMP_INFO_H
> > >
> > > >>
> > > >
> > > > Can you please spell out, in the commit message, the reason for
> > > > introducing a new header file? (I suspect your reason, but it should be
> > > > documented explicitly.)
> > >
> > > Also, should you have a copyright header in the new file? And does
> > > MAINTAINERS cover it?
> > >
> >
> > None of the dump support is covered. Based on commit history, I can suggest
> > Wen Congyang, as original author.
> > Sadly, Qiao Nuohan cannot be reached with his mail today (anyone knows if
> > he is still contributing?). Laszlo has done significant changes and reviews
> > too. I can also propose myself to help with reviews.
> >
> > Wen or Laszla, do you want to be the main maintainer?
>
> What about Peter Xu (CC'ed)? He'll have to state whether he has time and
> interest, but I see he's contributed quite a bit to dump.c.
I believe those were the first commits of mine when working on
detached dump, after that I didn't really work on it anymore. So I
guess I may not be the best candidate.
Also, I admit my bandwidth is limited as well recently. Thanks Drew
for mentioning me anyway. :-)
--
Peter Xu
next prev parent reply other threads:[~2017-06-06 2:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 13:03 [Qemu-devel] [PATCH v2 0/4] dump: add vmcoreinfo note Marc-André Lureau
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 1/4] dump: add DumpInfo structure Marc-André Lureau
2017-06-01 18:06 ` Laszlo Ersek
2017-06-01 18:18 ` Eric Blake
2017-06-02 9:46 ` Marc-André Lureau
2017-06-02 9:55 ` Marc-André Lureau
2017-06-02 22:49 ` Laszlo Ersek
2017-06-04 15:56 ` Zhang Chen
2017-06-06 18:19 ` Laszlo Ersek
2017-06-05 7:24 ` Andrew Jones
2017-06-06 2:11 ` Peter Xu [this message]
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 2/4] dump: add vmcoreinfo ELF note Marc-André Lureau
2017-06-01 18:38 ` Laszlo Ersek
2017-06-02 11:13 ` Marc-André Lureau
2017-06-06 14:21 ` Laszlo Ersek
2017-06-29 12:47 ` Marc-André Lureau
2017-06-05 8:04 ` Andrew Jones
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 3/4] kdump: add vmcoreinfo Marc-André Lureau
2017-06-05 8:07 ` Andrew Jones
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 4/4] scripts/dump-guest-memory.py: " Marc-André Lureau
2017-06-01 13:46 ` [Qemu-devel] [PATCH v2 0/4] dump: add vmcoreinfo note no-reply
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=20170606021156.GL4056@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=anderson@redhat.com \
--cc=drjones@redhat.com \
--cc=eblake@redhat.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wency@cn.fujitsu.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).