public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	andi@firstfloor.org, williams@redhat.com, schwidefsky@de.ibm.com,
	mingo@elte.hu, linux-tip-commits@vger.kernel.org
Subject: Re: [PATCH] acpi/pm: If failed at validating ACPI PM timer, inhibit future reads.
Date: Fri, 14 Jan 2011 08:33:49 -0800	[thread overview]
Message-ID: <1295022829.2655.18.camel@work-vm> (raw)
In-Reply-To: <alpine.LFD.2.00.1101141701360.2678@localhost6.localdomain6>

On Fri, 2011-01-14 at 17:02 +0100, Thomas Gleixner wrote:
> On Fri, 14 Jan 2011, john stultz wrote:
> 
> > On Fri, 2011-01-14 at 07:44 -0800, john stultz wrote:
> > > I'm actually looking at a different fix, as I'm worried by Thomas'
> > > comment about hitting the same issue on real hardware if we catch the
> > > same pmtrm value both times.
> > 
> > Konrad: Mind trying the following?
> > 
> > 
> > The conditional (!hpet && !ref_start && !ref_stop) doesn't really make
> > sense. If the refs are null, but hpet is on, we still want to break out.
> > 
> > So checking if both the ref values are the same should handle if we
> > don't have hardware (both null) or if they are the same value (either by
> > invalid hardware, or by chance), which can cause a divzero issue.
> > 
> > NOT FOR INCLUSION, I haven't had my coffee yet.
> > Signed-off-by: John Stultz <johnstul@us.ibm.com>
> > 
> > diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> > index 823f79a..fa2cb5e 100644
> > --- a/arch/x86/kernel/tsc.c
> > +++ b/arch/x86/kernel/tsc.c
> > @@ -935,7 +935,7 @@ static void tsc_refine_calibration_work(struct work_struct *work)
> >  	tsc_stop = tsc_read_refs(&ref_stop, hpet);
> >  
> >  	/* hpet or pmtimer available ? */
> > -	if (!hpet && !ref_start && !ref_stop)
> > +	if (ref_start == ref_stop)
> >  		goto out;
> >  
> >  	/* Check, whether the sampling was disturbed by an SMI */
> 
> That makes sense, though we really should kill pmtimer when we detect
> that it's crappy.

Agreed. 

thanks
-john


  reply	other threads:[~2011-01-14 16:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06  0:39 [PATCH] Greatly improve TSC calibration using a delayed workqueue John Stultz
2010-11-07 20:41 ` Andi Kleen
2010-11-08 22:04   ` john stultz
2010-11-09 13:43     ` Andi Kleen
2010-11-09 21:41       ` john stultz
2010-11-10 13:47         ` Andi Kleen
2010-12-05 11:18 ` [tip:x86/tsc] x86: Improve " tip-bot for John Stultz
2011-01-11  8:13   ` Kirill A. Shutemov
2011-01-11  8:26     ` Thomas Gleixner
2011-01-11  8:30       ` Kirill A. Shutemov
2011-01-11  8:37         ` Thomas Gleixner
2011-01-11  9:56           ` Kirill A. Shutemov
2011-01-11 10:26             ` Thomas Gleixner
2011-01-13 17:49             ` Konrad Rzeszutek Wilk
2011-01-13 18:01               ` john stultz
2011-01-13 21:40                 ` [PATCH] acpi/pm: If failed at validating ACPI PM timer, inhibit future reads Konrad Rzeszutek Wilk
2011-01-13 22:15                   ` Thomas Gleixner
2011-01-14 14:09                     ` Konrad Rzeszutek Wilk
2011-01-14 15:44                       ` john stultz
2011-01-14 15:54                         ` john stultz
2011-01-14 16:02                           ` Thomas Gleixner
2011-01-14 16:33                             ` john stultz [this message]
2011-01-14 16:28                           ` Konrad Rzeszutek Wilk

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=1295022829.2655.18.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=kirill@shutemov.name \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=schwidefsky@de.ibm.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tglx@linutronix.de \
    --cc=williams@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