From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexey Kardashevskiy <aik@au1.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Per process DSCR + somefixes (try#3)
Date: Wed, 02 Mar 2011 16:47:48 +1100 [thread overview]
Message-ID: <1299044868.8833.832.camel@pasglop> (raw)
In-Reply-To: <4D5B62F2.3020709@au1.ibm.com>
On Wed, 2011-02-16 at 16:38 +1100, Alexey Kardashevskiy wrote:
> step1: http://patchwork.ozlabs.org/patch/71489/
> step2: http://patchwork.ozlabs.org/patch/81423/
>
> In step2 I defined sysfs node as:
>
> static SYSDEV_ATTR(dscr_default, 0600, show_dscr_default,
> store_dscr_default);
>
> and it caused problems with rhel6.
> Now it is:
>
> static SYSDEV_CLASS_ATTR(dscr_default, 0600, show_dscr_default,
> store_dscr_default);
>
> It works now on both 2.6.32 and 2.6.36 but is that correct?
Ok, please resend with a proper changeset comment, something like that
would do:
<<
The DSCR (aka Data Stream Control Register) is supported on some
server PowerPC chips and allow some control over the prefetch
of data streams.
This patch allows the value to specified per thread by emulating
the corresponding mfspr and mtspr instructions. Children of such
threads inherit the value. Other threads use a default value that
can be specified in sysfs.
>>
And include your Signed-off-by: line.
BTW. I suppose it's an expected behaviour that thread created with a
given default value will keep that value even when the default is later
changed right ? And their descendents will use the same default as the
original thread, not the new default, at least that's how I read your
code :-) Maybe that should be documented somewhere...
Cheers,
Ben.
next prev parent reply other threads:[~2011-03-02 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 5:38 Per process DSCR + somefixes (try#3) Alexey Kardashevskiy
2011-02-21 2:44 ` Alexey Kardashevskiy
2011-03-02 5:47 ` Benjamin Herrenschmidt [this message]
2011-03-02 6:15 ` Alexey Kardashevskiy
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=1299044868.8833.832.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aik@au1.ibm.com \
--cc=linuxppc-dev@lists.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).