From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751115AbcBAX3R (ORCPT ); Mon, 1 Feb 2016 18:29:17 -0500 Received: from mga01.intel.com ([192.55.52.88]:61058 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750972AbcBAX3P (ORCPT ); Mon, 1 Feb 2016 18:29:15 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,382,1449561600"; d="scan'208";a="874483074" From: "Luck, Tony" To: Borislav Petkov , "H. Peter Anvin" , "Ingo Molnar" , Thomas Gleixner CC: Andy Lutomirski , Peter Zijlstra , Steven Rostedt , Brian Gerst , lkml Subject: RE: [RFC] Dump interesting arch/platform info Thread-Topic: [RFC] Dump interesting arch/platform info Thread-Index: AQHRXOeP2ofnCMF0NUOscwMAurVJjZ8X1NbQ Date: Mon, 1 Feb 2016 23:29:03 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F39FCE0E4@ORSMSX114.amr.corp.intel.com> References: <20160201115601.GD6438@pd.tnic> In-Reply-To: <20160201115601.GD6438@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYjcyMjIyZGQtNTA1OC00MDE0LTk0ZmQtNjViZGIwZDY5ODc4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiVlNHQnhPVG5HbmloVlNZYXErZlVYRHdoT2E2d3FHY2lvekdQT0ptSHRDVT0ifQ== x-ctpclassification: CTP_IC 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 u11NTMHP014309 > So the use case is you go, modprobe this thing and do > > cat /sys/kernel/debug/x86/archinfo > > Right now, it dumps only the GDT and even that is not fully done. But > more interesting stuff should be added to it as need arises. > > Thoughts, ideas, suggestions? On a high core count, multi-socket, machine I see almost 10K lines of output from this. If you add other things it will become a bit of a jumble to parse. Perhaps the module name "archinfo" is fine, but each separate thing it shows should get its own file. Starting with: /sys/kernel/debug/x86/gdtinfo for the current output? -Tony