From: David Daney <ddaney.cavm@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: "Steven J. Hill" <sjhill@mips.com>,
linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH v4] MIPS: Make CP0 config registers readable via sysfs.
Date: Thu, 13 Dec 2012 15:38:58 -0800 [thread overview]
Message-ID: <50CA6712.1060809@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1212132325180.5950@eddie.linux-mips.org>
On 12/13/2012 03:27 PM, Maciej W. Rozycki wrote:
> On Thu, 13 Dec 2012, Steven J. Hill wrote:
>
>> Allow reading of CP0 config registers via sysfs for each core
>> in the system. The registers will show up in sysfs at the path:
>>
>> /sys/devices/system/cpu/cpuX/configX
>
> You're exporting privileged context outside the kernel -- have all the
> security implications been considered?
Can you give an example of what would be risky?
> At the very least I don't think
> these files should be word-readable.
>
According to Steven's earlier comments, all he really cares about are
the ASEs implemented.
We have a patch (that I will send soon) that exports the Cache
configurations via the same method that x86 Cache information is
reported, so that part of the config register information would be
reported separately.
The rest of the CP0_ConfigX bits really report things that are only
useful to privileged mode software, so perhaps they shouldn't be reported.
David Daney
next prev parent reply other threads:[~2012-12-13 23:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:15 [PATCH v4] MIPS: Make CP0 config registers readable via sysfs Steven J. Hill
2012-12-13 23:27 ` Maciej W. Rozycki
2012-12-13 23:38 ` David Daney [this message]
2013-01-04 18:38 ` Hill, Steven
2013-01-04 19:05 ` David Daney
2013-01-04 19:30 ` Hill, Steven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50CA6712.1060809@gmail.com \
--to=ddaney.cavm@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sjhill@mips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.