From: Vivek Goyal <vgoyal@redhat.com>
To: CAI Qian <caiqian@redhat.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>,
kexec <kexec@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
crash-utility <crash-utility@redhat.com>
Subject: Re: [LTP] [RFC] autokdump - automated kdump testsuite
Date: Tue, 23 Sep 2014 08:09:59 -0400 [thread overview]
Message-ID: <20140923120959.GB1732@redhat.com> (raw)
In-Reply-To: <1446076274.27552759.1411440835273.JavaMail.zimbra@redhat.com>
On Mon, Sep 22, 2014 at 10:53:55PM -0400, CAI Qian wrote:
[..]
> > Why not simply let the respective service on the host do this job and
> > test only makes sure that kdump service is running. It feels little
> > out of place that a test is generating custom initramfs.
> Because not every distro will have a kdump service like Fedora.
So which distro does not have a service? Do we know this or we are
assuming that distributions don't have a service to load/unload
kdump kernel.
[..]
> > makedumpfile will reduce the vmcore file size to few hundreds of mega
> > bytes on most of the systems. Especially, this is just a test, so
> > system will be lightly loaded and vmcore will be small after filtering.
> It probably actually have test cases to heavily loaded the memory before
> dumping.
Your original proposal does not take care of this case either. A test
case could be heavily used memory and if user does not have sufficient
memory to save core, so be it. That test will fail.
Thanks
Vivek
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-09-23 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <145412866.25258463.1411119061796.JavaMail.zimbra@redhat.com>
2014-09-19 9:52 ` [LTP] [RFC] autokdump - automated kdump testsuite CAI Qian
2014-09-19 13:22 ` Vivek Goyal
2014-09-19 13:33 ` Vivek Goyal
2014-09-22 13:00 ` CAI Qian
2014-09-22 14:47 ` Vivek Goyal
2014-09-23 2:53 ` CAI Qian
2014-09-23 12:09 ` Vivek Goyal [this message]
2014-09-22 9:07 ` Dave Young
2014-09-22 9:12 ` Dave Young
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=20140923120959.GB1732@redhat.com \
--to=vgoyal@redhat.com \
--cc=caiqian@redhat.com \
--cc=crash-utility@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
/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