From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933132AbcKGSh4 (ORCPT ); Mon, 7 Nov 2016 13:37:56 -0500 Received: from mga06.intel.com ([134.134.136.31]:16778 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932635AbcKGShw (ORCPT ); Mon, 7 Nov 2016 13:37:52 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,606,1473145200"; d="scan'208";a="28475369" From: "Luck, Tony" To: Borislav Petkov CC: linux-edac , X86 ML , LKML Subject: RE: [PATCH] x86/MCE: Remove MCP_TIMESTAMP Thread-Topic: [PATCH] x86/MCE: Remove MCP_TIMESTAMP Thread-Index: AQHSN2YVreEusDrPO0C7vY93fGD+C6DNzSdAgACOKQD//4FTEA== Date: Mon, 7 Nov 2016 18:37:50 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F3A22728C@ORSMSX114.amr.corp.intel.com> References: <20161101120911.13163-1-bp@alien8.de> <20161105131104.drouavgezizz4w7v@pd.tnic> <3908561D78D1C84285E8C5FCA982C28F3A22720B@ORSMSX114.amr.corp.intel.com> <20161107180853.4uxlvtoychzhwr2q@pd.tnic> In-Reply-To: <20161107180853.4uxlvtoychzhwr2q@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id uA7IbxYx001985 > One other possibility would be to use ->time and write ->tsc *only* > when exact - i.e., in the handler - and this is then enough info about > timing. > > ->time will give you somewhere around where it happened and ->tsc - only > if set - will give you exact, well, *timestamp* :) > > This sounds like a pretty straightforward logic to me... Also to me ... and I think that's what used to happen (or at least was the intent). -Tony