On Thu, Mar 25, 2010 at 02:59:38PM +, Jukka Ruohonen wrote:
Log Message:
In addition to 'hz', document also 'tick', 'tickadj', 'stathz', and 'profhz'.
tick ok, the other: please don't. tickadj is an implementation detail of
the clock discipline code. stathz and profhz are not of any use to
On Thu, Mar 25, 2010 at 04:42:10PM +, Andrew Doran wrote:
Well wouldn't it then be better to document that they are not of
any use to the general kernel? From a quick look around, I see
also quite a few instances of stathz and profhz being
used/defined.
What Joerg said. They
On Thu, Mar 25, 2010 at 05:46:27PM +0200, Jukka Ruohonen wrote:
Well wouldn't it then be better to document that they are not of any use to
the general kernel? From a quick look around, I see also quite a few
instances of stathz and profhz being used/defined.
Sure, because each platform has a
David Holland dholland-sourcechan...@netbsd.org wrote:
What Joerg said. They are low level kernel implementation details.
These belong in a book or article or a wiki page or something, not the
manual.
We just went around on this like two or three weeks ago on spl
internals. On the
On Thu, Mar 25, 2010 at 04:50:03PM +, David Holland wrote:
We just went around on this like two or three weeks ago on spl
internals. On the one hand, the man page should document the
interface, not the implementation; on the other hand, anything global
someone might run across while
On Thu, Mar 18, 2010 at 1:12 AM, Masao Uebayashi uebay...@tombi.co.jp wrote:
On Tue, Mar 16, 2010 at 03:52:26AM +, YAMAMOTO Takashi wrote:
Why not adding VOP_GETPAGES_XIP - because XIP is almost transparent to
filesystems. The difference between XIP or not is only where to get pages,
On 3/24/10 7:32 PM, enami tsugutomo wrote:
The _lwp_ctl() call also need to be called with self-pt_lwpctl
doesn't it?
I thought pthread__first would be the same as pthread__self() here, but
when I just used pthread__first rather than calling pthread__self() I
got a different value.
I don't
On Thu, Mar 25, 2010 at 05:46:27PM +0200, Jukka Ruohonen wrote:
Well wouldn't it then be better to document that they are not of any use
to
the general kernel? From a quick look around, I see also quite a few
instances of stathz and profhz being used/defined.
Sure, because
On Wed, Mar 24, 2010 at 01:13:30AM +, David Young wrote:
Module Name: src
Committed By: dyoung
Date: Wed Mar 24 01:13:30 UTC 2010
Modified Files:
src/sys/dev/acpi: acpi_ec.c
src/sys/dev/isa: pas.c
Log Message:
Do not use unitialized bus_space_tag_t's. Use the
