On Mon, Aug 08, 2011 at 11:18:35AM +, Jared D. McNeill wrote:
Module Name: src
Committed By: jmcneill
Date: Mon Aug 8 11:18:34 UTC 2011
Modified Files:
src/sys/arch/x86/x86: tsc.c
Log Message:
If the USE_PLATFORM_CLOCK flag is set in the FADT, it indicates that OSPM
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
We should not really trust ACPI/FADT here. See acpicpu(4) how this is
Why?
derived from the actual CPU information. Additionally, I suggested decreasing
the quality of tsc(9) based on this information a long time ago, but joerg@
had concerns about
On Mon, Aug 08, 2011 at 07:40:45AM -0400, Jared McNeill wrote:
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
We should not really trust ACPI/FADT here. See acpicpu(4) how this is
Why?
Because we (the operating system) know this better than the BIOS writer.
And because this flag is not reliable;
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
Why?
Because we (the operating system) know this better than the BIOS writer.
And because this flag is not reliable; numerous systems where tsc(9) is
broken miss this flag in my ACPI table collection, and vice versa.
This flag is new in ACPI v3.0. If
On Mon, Aug 08, 2011 at 07:49:42AM -0400, Jared McNeill wrote:
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
Why?
Because we (the operating system) know this better than the BIOS writer.
And because this flag is not reliable; numerous systems where tsc(9) is
broken miss this flag in my ACPI
On Mon, Aug 08, 2011 at 08:16:43AM -0400, Jared McNeill wrote:
Newer systems with invariant TSC shouldn't set the USE_PLATFORM_CLOCK
flag.
But the do, unfortunately. Again, I have several examples from the field.
- Jukka.
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
Yes, but when possible, we should always prefer actual, reliable, CPU
information instead of the BIOS. Note also that at least with Intel CPUs,
the TSC should be entirely safe with the current stock-NetBSD (i.e. no
automatic CPU power management), but
On Mon, 8 Aug 2011, Jukka Ruohonen wrote:
On Mon, Aug 08, 2011 at 08:16:43AM -0400, Jared McNeill wrote:
Newer systems with invariant TSC shouldn't set the USE_PLATFORM_CLOCK
flag.
But the do, unfortunately. Again, I have several examples from the field.
I'd be willing to let
On Mon, Aug 08, 2011 at 03:03:41PM +0300, Jukka Ruohonen wrote:
Note also that at least with Intel CPUs,
the TSC should be entirely safe with the current stock-NetBSD (i.e. no
automatic CPU power management), but now you've marked it unreliable for
many systems (cf. also [1]).
Tell that to my
On Tue, 8 Mar 2011, Michael Lorenz wrote:
Modified Files:
src/sys/arch/x86/x86: x86_autoconf.c
lol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
On Mar 7, 2011, at 10:48 PM, Jared McNeill wrote:
On Tue, 8 Mar 2011, Michael Lorenz wrote:
Modified Files:
src/sys/arch/x86/x86: x86_autoconf.c
lol
I was tempted to add something like Yes Jared, hell did freeze over ;)
have
Module Name: src
Committed By: jruoho
Date: Fri Mar 4 04:53:28 UTC 2011
Modified Files:
src/sys/arch/x86/x86: est.c powernow.c
Log Message:
Raise the return value of the match-function of est(4) and powernow(4).
The assigned priorities are now: 10 for acpicpu(4), 5 for
On Fri, Mar 04, 2011 at 04:04:53PM +1100, matthew green wrote:
Raise the return value of the match-function of est(4) and powernow(4).
The assigned priorities are now: 10 for acpicpu(4), 5 for est(4) and
powernow(4), and 1 for odcm(4). These are used to pick the preferred driver.
to the
On Fri, Mar 04, 2011 at 04:04:53PM +1100, matthew green wrote:
Raise the return value of the match-function of est(4) and powernow(4).
The assigned priorities are now: 10 for acpicpu(4), 5 for est(4) and
powernow(4), and 1 for odcm(4). These are used to pick the preferred
driver.
Modified Files:
src/sys/arch/x86/x86: patch.c
Log Message:
Gracelessly bracket #include opt_spldebug.h with #ifdef i386.
Should fix the amd64 kernel-build failure that Andreas Wrede
reported.
perhaps __i386__
I think __i386__ or __x86_64__ for ${MACHINE_ARCH},
and i386 or amd64
In article 091104193344.m0225...@mirage.ceres.dti.ne.jp,
Izumi Tsutsui tsut...@ceres.dti.ne.jp wrote:
Modified Files:
src/sys/arch/x86/x86: patch.c
Log Message:
Gracelessly bracket #include opt_spldebug.h with #ifdef i386.
Should fix the amd64 kernel-build failure that Andreas Wrede
note that the kernel is built with -D${MACHINE}, last i looked.
On Nov 5, 12:26pm, m...@eterna.com.au (matthew green) wrote:
-- Subject: re: CVS commit: src/sys/arch/x86/x86
| note that the kernel is built with -D${MACHINE}, last i looked.
Should it, or should it rely just on the compiler defines?
the compiler does not and should
p...@whooppee.com said:
I guess maybe the minus signs shouldn't ever happen?
someone out here with a liquid nitrogen cooler?
best regards
Matthias
given that this issue is appearing on both ipmi and coretemp, and the
fact that coretemp doesn't even bother with hi/low limits, it's probably
something in envsys itself.
On Tue, 7 Jul 2009, Matthias Drochner wrote:
p...@whooppee.com said:
I guess maybe the minus signs shouldn't ever
101 - 120 of 120 matches
Mail list logo
