All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"pasha.tatashin@oracle.com" <pasha.tatashin@oracle.com>
Subject: Re: freedesktop bug id: 100548, bisected to sched/clock commit
Date: Thu, 13 Apr 2017 16:55:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1704131654130.2408@nanos> (raw)
In-Reply-To: <20170413132349.thxkwptdymsfsyxb@hirez.programming.kicks-ass.net>

On Thu, 13 Apr 2017, Peter Zijlstra wrote:
> On Thu, Apr 13, 2017 at 03:30:25PM +0300, Martin Peres wrote:
> > On 13/04/17 14:48, Peter Zijlstra wrote:
> > > On Wed, Apr 12, 2017 at 05:49:53PM +0300, Martin Peres wrote:
> > > 
> > > > Good to know. Is there a way to disable this behaviour, as a workaround for
> > > > our CI system until a proper fix lands? We already pushed locally the revert
> > > > for this patch, but that may affect other platforms which do not exhibit the
> > > > problem.
> > > 
> > > Blergh, so the patch is correct, but the __gtod_offset calculation is
> > > fed with absolute crap numbers due to 'circumstances' and then using it
> > > ends up being worse than not using it.
> > 
> > Thanks for taking this bug seriously!
> 
> So I've not actually dug out a Core2 machine, so have only tested this
> by poking random values into the TSC MSR on an otherwise 'good' machine.
> 
> Could you give it a go to see if it works for you?
> 
> Thomas, how much hate?

Well you know, how much I love TSC and its completely non-sensical
behaviour. If that's necessary to cure it, go for it.

Thanks,

	tglx


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-04-13 14:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 12:04 freedesktop bug id: 100548, bisected to sched/clock commit Lofstedt, Marta
2017-04-12 12:31 ` Peter Zijlstra
2017-04-12 13:30   ` Jani Nikula
2017-04-12 14:28     ` Peter Zijlstra
2017-04-12 13:40   ` Martin Peres
2017-04-12 14:32     ` Peter Zijlstra
2017-04-12 14:49       ` Martin Peres
2017-04-12 15:50         ` Peter Zijlstra
2017-04-13 11:48         ` Peter Zijlstra
2017-04-13 12:30           ` Martin Peres
2017-04-13 13:23             ` Peter Zijlstra
2017-04-13 14:55               ` Thomas Gleixner [this message]
2017-04-18 14:10               ` Lofstedt, Marta
2017-04-18 15:53                 ` Peter Zijlstra
2017-04-20 17:19                   ` Peter Zijlstra
2017-04-20 19:36                     ` Peter Zijlstra

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.1704131654130.2408@nanos \
    --to=tglx@linutronix.de \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pasha.tatashin@oracle.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.