xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH] x86: drop pointless uses of __func__ / __FUNCTION__
Date: Wed, 24 Aug 2016 16:34:35 -0400	[thread overview]
Message-ID: <20160824203435.GD23337@char.us.oracle.com> (raw)
In-Reply-To: <57BD70CB02000078001087AD@prv-mh.provo.novell.com>

On Wed, Aug 24, 2016 at 02:02:51AM -0600, Jan Beulich wrote:
> Non-debugging message text should be (and is in the cases here)
> distinguishable without also logging function names. Debugging message
> text, otoh, already includes file name and line number, so also
> logging function names is redundant. One relatively pointless debugging
> message gets removed altogether. In another case a mising log level

s/mising/missing/
> specifier gets added at once.

Which one? I was thinking it would be either one of these:

> --- a/xen/arch/x86/time.c
> +++ b/xen/arch/x86/time.c
> @@ -1467,8 +1467,7 @@ static int __init verify_tsc_reliability
>          tsc_check_reliability();
>          if ( tsc_max_warp )
>          {
> -            printk("%s: TSC warp detected, disabling TSC_RELIABLE\n",
> -                   __func__);
> +            printk("TSC warp detected, disabling TSC_RELIABLE\n");
>              setup_clear_cpu_cap(X86_FEATURE_TSC_RELIABLE);
>          }
>      }
> --- a/xen/arch/x86/xstate.c
> +++ b/xen/arch/x86/xstate.c
> @@ -574,8 +574,8 @@ void xstate_init(struct cpuinfo_x86 *c)
>           * We know FP/SSE and YMM about eax, and nothing about edx at present.
>           */
>          xsave_cntxt_size = _xstate_ctxt_size(feature_mask);
> -        printk("%s: using cntxt_size: %#x and states: %#"PRIx64"\n",
> -            __func__, xsave_cntxt_size, xfeature_mask);
> +        printk("xstate: size: %#x and states: %#"PRIx64"\n",
> +               xsave_cntxt_size, xfeature_mask);
>  
>          asm ( "fxsave %0" : "=m" (ctxt) );
>          if ( ctxt.mxcsr_mask )
> 
>

but both just remove the __func__ usage? 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-24 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  8:02 [PATCH] x86: drop pointless uses of __func__ / __FUNCTION__ Jan Beulich
2016-08-24 20:34 ` Konrad Rzeszutek Wilk [this message]
2016-08-25  6:48   ` Jan Beulich
2016-08-31 18:43 ` Andrew Cooper
2016-09-01  7:17   ` Jan Beulich
2016-09-01  9:52     ` Andrew Cooper

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=20160824203435.GD23337@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).