From: Baoquan He <bhe@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org, kumagai-atsushi@mxc.nes.nec.co.jp
Subject: Re: [PATCH v5 8/8] add a new interface to show the memory usage of 1st kernel
Date: Tue, 26 Aug 2014 14:37:09 +0800 [thread overview]
Message-ID: <20140826063709.GC15032@dhcp-16-116.nay.redhat.com> (raw)
In-Reply-To: <20140825200418.GK14379@redhat.com>
On 08/25/14 at 04:04pm, Vivek Goyal wrote:
> On Mon, Aug 25, 2014 at 02:36:22PM +0800, Baoquan He wrote:
> > The print is like below:
> >
> > ~$ ./makedumpfile --mem-usage /proc/kcore
> > The kernel version is not supported.
> > The created dumpfile may be incomplete.
>
> I still think that above messages should go. It does not make
> any sense with --mem-usage. No dumpfile is being created here.
This is printed by function get_kernel_version(), it will be used by
other makedumpfile main code flows too. This message is used to warn
users that users' using kernel may not be tested suffciently. I think
those tests are mainly taken by Atsushi. When he finished sufficient
tests on a new version of kernel, the LATEST_VERSION will be changed to
be a larger value. I am fine with this message, since it won't occur on
our distribution, anyway kernel for distribution are all tested. And if
LATEST_VERSION is older than our distribution kernel, maintainer may be
pushed to take tests and update this value. So don't worry about this
message.
But I would like to change the message like below to clean up
misunderstanding if Atsushi doesn't object, this mostly occur when
people working on latest upstream kernel.
-------------------------------------------------
The kernel version is not supported.
The makedumpfile operation may not be successful.
--------------------------------------------------
>
> > Excluding unnecessary pages : [100.0 %] |
>
>
> >
> > Page number of memory in different use
> > --------------------------------------------------
>
> I think above header can completely go away. It kind of looks odd.
OK, will remove it.
>
> > TYPE PAGES EXCLUDABLE DESCRIPTION
> > ZERO 29149 yes Pages filled with zero
> > CACHE 171288 yes Cache pages
> > CACHE_PRIVATE 12051 yes Cache pages + private
> > USER 31816 yes User process pages
> > FREE 3700059 yes Free pages
> > KERN_DATA 105305 no Dumpable kernel data
> >
> > Total pages on system: 4049668
> >
> > Showing page number of memory in different use successfully.
>
> I think we don't need above line. I am not even sure what does it mean.
Will remove it.
> >
> > makedumpfile Completed.
>
> We don't need above line either.
This is also a public message printing, means if makedumpfile operation
is successful or not. Maybe I can add a check like below:
@@ -9546,7 +9553,7 @@ main(int argc, char *argv[])
retcd = COMPLETED;
out:
MSG("\n");
- if (retcd == COMPLETED)
+ if ((retcd == COMPLETED) && (!info->flag_mem_usage))
MSG("makedumpfile Completed.\n");
else
MSG("makedumpfile Failed.\n");
Hi Atsushi,
How do you think about this? And for the excluding progress indication
too, add a check that if it's mem-usage handling, not printing.
Thanks
Baoquan
>
> In output we should just show the actual table. If there is an error,
> we should output error and exit (no table).
>
> Thanks
> Vivek
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-08-26 6:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 3:33 [PATCH v4 0/8] add a new interface to show the memory usage of 1st kernel Baoquan He
2014-08-25 3:33 ` [PATCH v4 1/8] initialize pfn_memhole in get_num_dumpable_cyclic Baoquan He
2014-08-25 3:33 ` [PATCH v4 2/8] functions to get crashkernel memory range Baoquan He
2014-08-25 3:33 ` [PATCH v4 3/8] preparation functions for parsing vmcoreinfo Baoquan He
2014-08-25 5:45 ` [PATCH v5 " Baoquan He
2014-08-25 6:33 ` [PATCH v4 " Baoquan He
2014-08-25 3:33 ` [PATCH v4 4/8] set vmcoreinfo for kcore Baoquan He
2014-08-25 3:33 ` [PATCH v4 5/8] prepare the dump loads for kcore analysis Baoquan He
2014-08-25 3:33 ` [PATCH v4 6/8] introduce a function exclude_zero_pages_cyclic() Baoquan He
2014-08-25 3:33 ` [PATCH v4 7/8] implement a function to print the memory usage Baoquan He
2014-08-25 3:33 ` [PATCH v4 8/8] add a new interface to show the memory usage of 1st kernel Baoquan He
2014-08-25 6:36 ` [PATCH v5 " Baoquan He
2014-08-25 20:04 ` Vivek Goyal
2014-08-26 6:37 ` Baoquan He [this message]
2014-08-26 13:10 ` Vivek Goyal
2014-08-27 0:32 ` Atsushi Kumagai
2014-08-29 9:37 ` bhe
2014-08-25 7:03 ` [PATCH v4 " Baoquan He
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=20140826063709.GC15032@dhcp-16-116.nay.redhat.com \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=vgoyal@redhat.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