Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Corey Minyard <minyard@acm.org>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
	Dave Anderson <anderson@redhat.com>
Subject: Re: Tool for creating full vmcore
Date: Thu, 13 Feb 2014 12:07:47 -0500	[thread overview]
Message-ID: <20140213170747.GJ30844@redhat.com> (raw)
In-Reply-To: <52FCF69C.2080108@acm.org>

On Thu, Feb 13, 2014 at 10:45:16AM -0600, Corey Minyard wrote:

[..]
> >>
> >> I guess if code is small enough, then it might be useful to 
> >> keep it in a direcotry say kexec-tools/vmcore-kcore. But if it turns
> >> out to be big, it might be better to maintain it as a separate project
> >> (like makedumpfile).
> 
> Yeah, it's a little big, but not huge.  Most of the code is the elf
> part, which is in it's own file and could be a separate library.  I'm
> fine either way.  It will get bigger as new arch-specific code is added.

This does sound like significant code when other arch support is added.
I am beginning to think if it better to manage it as a separate project
in separate git tree.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2014-02-13 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 20:21 Tool for creating full vmcore Corey Minyard
2014-02-12 21:42 ` Vivek Goyal
     [not found]   ` <CADq4U7+K-Zi2Ckb-mfDWFf50Oq7hbTWR6H92=Jx=STqWSJu89g@mail.gmail.com>
     [not found]     ` <20140213135153.GB30844@redhat.com>
2014-02-13 13:52       ` Vivek Goyal
2014-02-13 16:45         ` Corey Minyard
2014-02-13 17:07           ` Vivek Goyal [this message]
2014-02-13  9:26 ` Louis Bouchard

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=20140213170747.GJ30844@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=anderson@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=minyard@acm.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