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 S1754721AbbEUJlu (ORCPT <rfc822;w@1wt.eu>);
	Thu, 21 May 2015 05:41:50 -0400
Received: from www.linutronix.de ([62.245.132.108]:37670 "EHLO
	Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751385AbbEUJlq (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 21 May 2015 05:41:46 -0400
Date: Thu, 21 May 2015 11:41:50 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Andy Lutomirski <luto@kernel.org>
cc: Huang Rui <ray.huang@amd.com>, Borislav Petkov <bp@suse.de>,
        Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        x86@kernel.org, linux-kernel@vger.kernel.org,
        Fengguang Wu <fengguang.wu@intel.com>, Aaron Lu <aaron.lu@intel.com>,
        Tony Li <tony.li@amd.com>, Peter Zijlstra <peterz@infradead.org>,
        John Stultz <john.stultz@linaro.org>
Subject: Re: [RFC PATCH 2/4] x86, mwaitt: introduce mwaitx idle with a
 configurable timer
In-Reply-To: <555D3629.8080002@kernel.org>
Message-ID: <alpine.DEB.2.11.1505211035291.4225@nanos>
References: <1432022472-2224-1-git-send-email-ray.huang@amd.com> <1432022472-2224-3-git-send-email-ray.huang@amd.com> <555D3629.8080002@kernel.org>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Linutronix-Spam-Score: -1.0
X-Linutronix-Spam-Level: -
X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required,  ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 20 May 2015, Andy Lutomirski wrote:
> John, Peter, Thomas: would it actually make sense to teach the core
> timer/clockevent code about perfect time sources like invariant TSC + TSC

Perfect? There is no such concept in timer land.

> deadline?  AFAICT right now we're not doing anything particularly interesting
> with the TSC deadline timer.

Interesting in what way? We still have to convert from and to
nanoseconds and deal with the clock skew ....

Thanks,

	tglx