linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	John Stultz <john.stultz@linaro.org>,
	x86@kernel.org
Subject: Re: [PATCH] x86, clocksource, fix !CONFIG_CLOCKSOURCE_WATCHDOG compile
Date: Mon, 27 May 2013 17:29:49 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1305271729170.4220@ionos> (raw)
In-Reply-To: <51A36FB3.9050607@redhat.com>

On Mon, 27 May 2013, Prarit Bhargava wrote:

> 
> 
> On 05/27/2013 06:00 AM, Thomas Gleixner wrote:
> > On Fri, 22 Feb 2013, Prarit Bhargava wrote:
> > 
> >> If I explicitly disable the clocksource watchdog in the x86 Kconfig,
> > 
> > And why do you want to do that?
> 
> Hey Thomas, I was debugging something and stumbled across this.
> 
> IIRC the issue was that there some weirdness on a series of new AMD systems and
> unfortunately the watchdog would fire and switch clocksources on me :(  That
> resulted in me not being able to debug the HW because the clocksource I wanted
> was no longer available.

tsc=reliable on the kernel command line kills the watchdog
requirement.

Thanks,

	tglx

  reply	other threads:[~2013-05-27 15:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-22 20:08 [PATCH] x86, clocksource, fix !CONFIG_CLOCKSOURCE_WATCHDOG compile Prarit Bhargava
2013-02-22 20:14 ` Thomas Gleixner
2013-02-24 17:04   ` Prarit Bhargava
2013-02-25 14:21     ` Prarit Bhargava
2013-02-25 15:01   ` Prarit Bhargava
2013-05-27 10:00 ` Thomas Gleixner
2013-05-27 14:37   ` Prarit Bhargava
2013-05-27 15:29     ` Thomas Gleixner [this message]
2013-07-22 23:01 ` John Stultz

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.LFD.2.02.1305271729170.4220@ionos \
    --to=tglx@linutronix.de \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=x86@kernel.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).