mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Zhenzhong Duan <zhenzhong.duan@oracle.com>
Cc: mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Calling check_system_tsc_reliable before unsynchronized_tsc
Date: Tue, 20 Jun 2017 15:14:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1706201512020.1869@nanos> (raw)
In-Reply-To: <3fbce128-1468-45f1-2f54-974132553177@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]

On Tue, 13 Jun 2017, Zhenzhong Duan wrote:
> 在 2017/6/13 0:03, Thomas Gleixner 写道:
> > On Thu, 8 Jun 2017, Zhenzhong Duan wrote:
> > 
> > > unsynchronized_tsc() checks value of tsc_clocksource_reliable which is set
> > > by
> > > check_system_tsc_reliable(). It's better to move
> > > check_system_tsc_reliable()
> > > at
> > > front, or else this check makes no sense.
> > > 
> > > Though X86_FEATURE_CONSTANT_TSC is usually set for TSC reliable system,
> > > just
> > > in
> > > case.
> > > 
> > > Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
> > > ---
> > >   arch/x86/kernel/tsc.c |    4 ++--
> > >   1 files changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> > > index 714dfba..a316bdd 100644
> > > --- a/arch/x86/kernel/tsc.c
> > > +++ b/arch/x86/kernel/tsc.c
> > > @@ -1412,11 +1412,11 @@ void __init tsc_init(void)
> > >    	use_tsc_delay();
> > >   +	check_system_tsc_reliable();
> > > +
> > >   	if (unsynchronized_tsc())
> > >   		mark_tsc_unstable("TSCs unsynchronized");
> > >   -	check_system_tsc_reliable();
> > > -
> > What kind of patch is that? Definitely nothing which can be applied.
> To avoid using unassigned variable tsc_clocksource_reliable.
> Or what's the purpose of if (tsc_clocksource_reliable) check in
> unsynchronized_tsc()?

That's not the question. The patch format itself is broken:

@@ -1412,11 +1412,11 @@ void __init tsc_init(void)
    	use_tsc_delay();
  +	check_system_tsc_reliable();
+
  	if (unsynchronized_tsc())
   		mark_tsc_unstable("TSCs unsynchronized");
  -	check_system_tsc_reliable();
-

That is not a patch created with diff -u or any other mechanism
which creates properly formatted patches.

Thanks,

	tglx

      reply	other threads:[~2017-06-20 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 11:43 Zhenzhong Duan
2017-06-12 16:03 ` Thomas Gleixner
2017-06-13  2:47   ` Zhenzhong Duan
2017-06-20 13:14     ` Thomas Gleixner [this message]

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=alpine.DEB.2.20.1706201512020.1869@nanos \
    --to=tglx@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=x86@kernel.org \
    --cc=zhenzhong.duan@oracle.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®