From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1757954AbcLONNG (ORCPT <rfc822;w@1wt.eu>);
        Thu, 15 Dec 2016 08:13:06 -0500
Received: from bombadil.infradead.org ([198.137.202.9]:45985 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1757439AbcLONNE (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 15 Dec 2016 08:13:04 -0500
Message-Id: <20161215130454.914605806@infradead.org>
User-Agent: quilt/0.63-1
Date: Thu, 15 Dec 2016 14:04:54 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: tglx@linutronix.de, mingo@kernel.org, rafael@kernel.org,
        nmorey@kalray.eu
Cc: srinivas.pandruvada@linux.intel.com, jacob.jun.pan@linux.intel.com,
        linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: [RFC][PATCH 0/4] sched_clock vs TSC wreckage
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


A few weeks ago Nicolas reported some impressive TSC wreckage on his i7-3820
running on an AsusTek Rampage IV Gene board [*].

These are a few patches that should hopefully allow us to do better in the face
of such 'creativity'.

[*] to be fair, Asus did in fact release a BIOS update that fixes this issue.