Hi,
I'm looking at 2.6.25-rc2. vsyscall_sysctl_change contains code to NOP
out the actual system call instructions of the vsyscall page when
vsyscall64 is enabled. This seems to interact badly with the fallback
code in do_vgettimeofday which tries to call gettimeofday if the
configured clock sou
Andi Kleen <[EMAIL PROTECTED]> writes:
> On Wed, Feb 20, 2008 at 02:57:34PM +0100, Arne Georg Gleditsch wrote:
>> Hi,
>>
>> I'm looking at 2.6.25-rc2. vsyscall_sysctl_change contains code to NOP
>> out the actual system call instructions of the vsyscall pag
dean gaudet <[EMAIL PROTECTED]> writes:
> on AMD x86 pre-family 10h the boundary is 8 bytes, and on fam 10h it's 16
> bytes. the penalty is a mere 3 cycles if an access crosses the specified
> boundary.
Worth noting though, is that atomic accesses that cross cache lines on
an Opteron system is
"J.A. Magallón" <[EMAIL PROTECTED]> writes:
> Software Memory Hole
> When "Enabled", allows software memory remapping around the memory
> hole. Options are Enabled and Disabled.
>
> Hardware Memory Hole
> When "Enabled", allows software memory remapping around the memory
> hole. Options are Enabled
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> You're missing the point. How will the PCI bus transactions be
> different when using MMCONFIG versus your extended CF8 version?
Conceivably this is useful if the IO hub does not support MMCONFIG
accesses. The AMD 8111 does not, as far as I can see
"Yinghai Lu" <[EMAIL PROTECTED]> writes:
> mmconfig is set in NB ( in new CPU), Do we still need to set mmconfig
> in SB like mcp55?
I wasn't aware that the family 10h-chips had MSRs for setting the
mmconfig address space directly in the NB (core?). Please disregard
my previous comment...
--
Randy Dunlap <[EMAIL PROTECTED]> writes:
> OTOH, you also didn't supply a patch. If you do this, I'll be
> glad to consider it. If I can read it, that is.
I like bash as much as the next guy, but (to my surprise) /bin/sh on
my current workstation is actually dash. How about just replacing the
s
[EMAIL PROTECTED] writes:
> I like lxr pretty much. i`m not a programmer, but i often need some
> information on "what`s the driver version of xyz in latest kernel" or
> "was this or that feature/patch already being merged" or "i have this
> line of code in kernel - how does it look in recent kern
Randy Dunlap <[EMAIL PROTECTED]> writes:
> On Tue, 26 Jun 2007 19:25:00 +0200 Julio M. Merino Vidal wrote:
>> The correct expression could be $((${a} + 2)). Tested under NetBSD's
>> sh, which is very POSIX-compliant.
>
> Thanks. Does anyone see other changes that are needed?
[..]
> and the co
Florian Attenberger <[EMAIL PROTECTED]> writes:
> there was one 'special' event at that date:
> syslog.2.gz:Jul 1 01:59:59 master kernel: Clock: inserting leap second
> 23:59:60 UTC
As far as I can tell, no leap second was due to be inserted at 1. of
July this year. Is the year set correctly for
Florian Attenberger <[EMAIL PROTECTED]> writes:
> yep, controlled by ntpd.
> You're right according to
> ftp://hpiers.obspm.fr/iers/bul/bulc/bulletinc.33
> that event shouldn't have been there.
I'm not all that versed in ntp-ish, but it appears that the leap
second insertion should be propagated t
"John Anthony Kazos Jr." <[EMAIL PROTECTED]> writes:
> Did this file individually, per request. Will re-do the whole tree later
> as I'm still working on my handy-dandy testing and patching tools and
> don't have a lot of time outside of work until the summer gets underway.
While this is probabl
"John Anthony Kazos Jr." <[EMAIL PROTECTED]> writes:
> Besides, based on the actual binary representation of UTF-8, it's
> extremely unlikely for any ISO-8859-1 string to be detected as UTF-8. VIm
> already does this: UTF-8 it handles natively, but open up one of these
> unpatched files in VIm a
Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> + case RTC_SPEED_UP:
> + err = rtc_speed_up(rtc);
> + break;
> +
> + case RTC_SLOW_DOWN:
> + err = rtc_speed_up(rtc);
> + break;
This doesn't look quite right. rtc_slow_down, surely?
--
14 matches
Mail list logo
