Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752857Ab3EJNIy (ORCPT ); Fri, 10 May 2013 09:08:54 -0400 Received: from tx2ehsobe003.messaging.microsoft.com ([65.55.88.13]:9157 "EHLO tx2outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751247Ab3EJNIw (ORCPT ); Fri, 10 May 2013 09:08:52 -0400 X-Forefront-Antispam-Report: CIP:157.56.236.101;KIP:(null);UIP:(null);IPV:NLI;H:BY2PRD0510HT003.namprd05.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -6 X-BigFish: PS-6(zz98dI936eI1432I13e6Kzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz8275bh8275dhz2fh2a8h668h839h93fhd24hd2bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1155h) From: Matthew Garrett To: "Ren, Qiaowei" CC: "linux-kernel@vger.kernel.org" , "platform-driver-x86@vger.kernel.org" , "Wei, Gang" Subject: Re: [PATCH 4/4] driver: provide sysfs interfaces to access SMX parameter Thread-Topic: [PATCH 4/4] driver: provide sysfs interfaces to access SMX parameter Thread-Index: AQHOSvE+ysMfIHdI9EqG5gcExdaKwpj6wt+AgAMpG0CAAHzgAA== Date: Fri, 10 May 2013 13:07:48 +0000 Message-ID: <1368191268.2425.38.camel@x230> References: <1367938519-840-1-git-send-email-qiaowei.ren@intel.com> <1367938519-840-5-git-send-email-qiaowei.ren@intel.com> <1367990697.2425.33.camel@x230> <9E0BE1322F2F2246BD820DA9FC397ADE9AC926@SHSMSX102.ccr.corp.intel.com> In-Reply-To: <9E0BE1322F2F2246BD820DA9FC397ADE9AC926@SHSMSX102.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.255.84.4] Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 X-OriginatorOrg: nebula.com 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 r4AD8wtm022024 Content-Length: 1061 Lines: 22 On Fri, 2013-05-10 at 07:05 +0000, Ren, Qiaowei wrote: > On 2013-05-08, Matthew Garrett wrote: > > On Tue, 2013-05-07 at 22:55 +0800, Qiaowei Ren wrote: > > > > > +What: /sys/devices/platform/intel_txt/parameter/acm_max_size > > > +Date: May 2013 > > > +KernelVersion: 3.9 > > > +Contact: "Qiaowei Ren" > > > +Description: The "acm_max_size" property will show max size of > > > + authenticated code execution area. > > > > What would userspace use this for? > > These sysfs files are just export SMX & TXT related information to userspace. So that other developers (or OSV & ISV) can be able to develop txt related applications or tools based on these information. If they're only using it for debugging purposes then sysfs probably isn't the right place. Is there any reason tools would need to know this during normal usage? -- Matthew Garrett | mjg59@srcf.ucam.org ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?