From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org
Subject: how to implement platform specific per process parameter?
Date: Mon, 06 Aug 2012 15:08:28 +1000 [thread overview]
Message-ID: <501F514C.2090909@ozlabs.ru> (raw)
Hi!
There is a per core register on modern POWER processors (POWER6+) called
"DSCR": The DSCR (aka Data Stream Control Register) is supported on some
server PowerPC chips and allow some control over the prefetch of data
streams.
Its "per process" support has been added by
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=efcac6589a277c10060e4be44b9455cf43838dc1
"powerpc: Per process DSCR + some fixes (try#4)"
The patch adds the DSCR value into "struct thread_struct" and
saves/restores it when the context is switched. Also, there is some policy
to initialize the register when a thread starts. So far so good.
Here is the problem.
Some customer(s) of this feature want an ability to change the DSCR value
of the already running process. I.e. we need some kernel interface which
would accept pid and the register value and change it.
There are 4 options:
1. [not a kernel interface] use ptrace to execute the register changing
command inside the specified pid. The next context switch saves the new
value in the thread_struct. Dirty hack.
2. Add a new syscall which would receive pid + register value and do the
job. A bit too much.
3. Add some hook in /proc filesystem but so far there were no platform
specific bits, right?
4. Implement a static node "/sys/devices/system/cpu/dscr_control". write()
would parse the input stream, call scanf("%d %x", &pid, &dscr) and do the job.
What is the correct approach? Thanks.
--
Alexey
next reply other threads:[~2012-08-06 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 5:08 Alexey Kardashevskiy [this message]
2012-08-06 7:57 ` how to implement platform specific per process parameter? Anshuman Khandual
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=501F514C.2090909@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).