From: Dave Young <dyoung@redhat.com>
To: Minfei Huang <mhuang@redhat.com>
Cc: Minfei Huang <mnfhuang@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
akpm@linux-foundation.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kexec: Add prefix "kexec" to output message
Date: Wed, 23 Sep 2015 09:37:24 +0800 [thread overview]
Message-ID: <20150923013723.GA4394@dhcp-129-160.nay.redhat.com> (raw)
In-Reply-To: <20150922160704.GA10225@dhcp-128-25.nay.redhat.com>
On 09/23/15 at 12:07am, Minfei Huang wrote:
> On 09/15/15 at 11:08am, Minfei Huang wrote:
> > On 09/14/15 at 04:44pm, Dave Young wrote:
> > > On 09/14/15 at 03:50pm, Minfei Huang wrote:
> > > > On 09/13/15 at 11:52am, Eric W. Biederman wrote:
> > > > > Minfei Huang <mnfhuang@gmail.com> writes:
> > > > >
> > > > > > kexec output message misses the prefix "kexec", when Dave Young split
> > > > > > the kexec code. To keep the same format, add the prefix "kexec" to
> > > > > > output message.
> > > > >
> > > > > What of kexec_core? What of the messages that already have a prefix?
> > > > >
> > > >
> > > > Hi, Eric.
> > > >
> > > > Last commit(2965fa), Dave Young (dyoung@redhatcom) split the previous
> > > > kernel/kexec.c into three pieces(kexec_core.c, kexec_file.c, kexec.c).
> > > > The common functions used by both kexec and kexec_file are placed in
> > > > file kernel/kexec_core.c.
> > > >
> > > > The format of the output message likes "kexec: SYSC_kexec_load: hello,
> > > > world" previously. Due to the missing prefix "kexec", now it like
> > > > "SYSC_kexec_load: hello, world".
> > > >
> > > > Dave Young misses the Macro pr_fmt to define the prefix output message
> > > > in file kexec.c and kexec_file.c. I think the previous Macro was moved
> > > > into the file kexec_core.c when Dave did the splitting.
> > >
> > > I'm not sure it is proper to add prefix "kexec: " in all kexec*.c, so
> > > only keep it in kexec_core.c.
> > >
> > > There's already printks with prefix like "Kexec:", "crashkernel:" and
> > > other strings. Adding another prefix before them looks odd. So either remove
> > > the prefix in kexec_core, or remove other prefixes already exists in kexec*.c
> > > I would prefix to remove the "kexec:" prefix in kexec_core.c
> >
> > Hi, Dave.
> >
> > How about removing all of the prefix "crashkernel" in kexec_core. Thus
> > we can be consistent with the output message prefix "kexec".
>
> Ping, any comment is appreciate and helpful.
Remove "crashkernel" sounds not a proper way, it indicates crashkernel parsing
messages. I have no idea what is the best way but below modification sounds better to me:
kexec_core.c:
#define pr_fmt(fmt) "[kexec_core] " fmt
Also remove below prefix "Kexec:"
pr_warn("Kexec: Memory allocation for saving cpu register states failed\n");
kexec.c:
#define pr_fmt(fmt) "[kexec] " fmt
kexec_file.c:
#define pr_fmt(fmt) "[kexec_file] " fmt
Thanks
Dave
next prev parent reply other threads:[~2015-09-23 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 7:15 Minfei Huang
2015-09-13 16:52 ` Eric W. Biederman
2015-09-14 7:50 ` Minfei Huang
2015-09-14 8:44 ` Dave Young
2015-09-15 3:08 ` Minfei Huang
2015-09-22 16:07 ` Minfei Huang
2015-09-23 1:37 ` Dave Young [this message]
2015-09-23 2:49 ` Baoquan He
2015-09-23 5:14 ` Minfei Huang
2015-09-23 5:26 ` Baoquan He
2015-09-23 5:44 ` Minfei Huang
2015-09-23 7:01 ` 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=20150923013723.GA4394@dhcp-129-160.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.com \
--cc=mnfhuang@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
all inboxes | Powered by JetHome®