[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1368191268.2425.38.camel@x230>
Date: Fri, 10 May 2013 13:07:48 +0000
From: Matthew Garrett <matthew.garrett@...ula.com>
To: "Ren, Qiaowei" <qiaowei.ren@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"platform-driver-x86@...r.kernel.org"
<platform-driver-x86@...r.kernel.org>,
"Wei, Gang" <gang.wei@...el.com>
Subject: Re: [PATCH 4/4] driver: provide sysfs interfaces to access SMX
parameter
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" <qiaowei.ren@...el.com>
> > > +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@...f.ucam.org
Powered by blists - more mailing lists