« Return to Thread: k10h post-BIOS patch effects
Re: k10h post-BIOS patch effects
by dean gaudet-2
::
Rate this Message:
On Sun, 20 Jul 2008, Clint Whaley wrote:
> Dean (& guys),
>
> OK, here are a few things. First, there is a modified xdfc available at:
> www.cs.utsa.edu/~whaley/dload/xdfc
> It is my normal kernel timer, which has been modified to keep calling the K10h
> kernel 1K times. When I run this on my Phenom, most of the numbers are roughly
> 8Gflop, but then it drops to 4Gflop for a lot of them. Can anyone with a
> Phenom run this executable and make sure yours doesn't do this to you too
> (i.e. the perf drop happens rarely enough that it can be missed)?
it seems to be 8.4gflop for my 2.3ghz pheonm:
# ./xdfc
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8366.61
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.58
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.81
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8376.21
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.64
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.92
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.55
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.40
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.10
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8376.29
...
i've let it run for a couple minutes now, no changes... actually it
finished, still no significant changes in the mflop -- it climbed a tiny
amount:
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.313, mflop=8391.98
dNB=40, time=0.313, mflop=8394.20
> >if you want to experiment with the workarounds, build
> >http://code.google.com/p/iotools/ and put it into your PATH.
> >
> >then execute a script something like this:
> >
> >for cpu in `awk '/^processor/ {print $3}' /proc/cpuinfo`; do
> > # disable erratum 298 workaround
> > wrmsr $cpu 0xc0010015 $(and $(rdmsr $cpu 0xc0010015) $(not $(shl 1 3)))
> > wrmsr $cpu 0xc0011023 $(and $(rdmsr $cpu 0xc0011023) $(not $(shl 1 1)))
> >
> > # disable erratum 309 workaround
> > wrmsr $cpu 0xc0011023 $(and $(rdmsr $cpu 0xc0011023) $(not $(shl 1 23)))
> >done
>
> This program allows you to change stuff in the BIOS on the fly? Or is this
> linux workarounds I need to be able to apply with an unpatched BIOS? I
> guess I need to check it out with savana & compile it (I didn't see any
> simple download link)?
yeah you probably need to check it out with svn and build it.
you probably also need to "modprobe msr".
the BIOS workarounds for those errata amount to setting those bits (i.e.
bit 3 of MSR 0xc0010015, bit 1 of 0xc0011023 and bit 23 of 0xc0011023)
... for these specific workarounds we can tweak them dynamically. if you
execute that script i pasted you'll disable the workarounds... which
will make your B2 behave like a B3.
-dean
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Math-atlas-devel mailing list
Math-atlas-devel@...
https://lists.sourceforge.net/lists/listinfo/math-atlas-devel
> Dean (& guys),
>
> OK, here are a few things. First, there is a modified xdfc available at:
> www.cs.utsa.edu/~whaley/dload/xdfc
> It is my normal kernel timer, which has been modified to keep calling the K10h
> kernel 1K times. When I run this on my Phenom, most of the numbers are roughly
> 8Gflop, but then it drops to 4Gflop for a lot of them. Can anyone with a
> Phenom run this executable and make sure yours doesn't do this to you too
> (i.e. the perf drop happens rarely enough that it can be missed)?
it seems to be 8.4gflop for my 2.3ghz pheonm:
# ./xdfc
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8366.61
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.58
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.81
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8376.21
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.64
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.92
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.55
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.40
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8377.10
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.314, mflop=8376.29
...
i've let it run for a couple minutes now, no changes... actually it
finished, still no significant changes in the mflop -- it climbed a tiny
amount:
dNB=40, ld=40,40,40, mu=4, nu=4, ku=1, lat=4, pf=0: time=0.313, mflop=8391.98
dNB=40, time=0.313, mflop=8394.20
> >if you want to experiment with the workarounds, build
> >http://code.google.com/p/iotools/ and put it into your PATH.
> >
> >then execute a script something like this:
> >
> >for cpu in `awk '/^processor/ {print $3}' /proc/cpuinfo`; do
> > # disable erratum 298 workaround
> > wrmsr $cpu 0xc0010015 $(and $(rdmsr $cpu 0xc0010015) $(not $(shl 1 3)))
> > wrmsr $cpu 0xc0011023 $(and $(rdmsr $cpu 0xc0011023) $(not $(shl 1 1)))
> >
> > # disable erratum 309 workaround
> > wrmsr $cpu 0xc0011023 $(and $(rdmsr $cpu 0xc0011023) $(not $(shl 1 23)))
> >done
>
> This program allows you to change stuff in the BIOS on the fly? Or is this
> linux workarounds I need to be able to apply with an unpatched BIOS? I
> guess I need to check it out with savana & compile it (I didn't see any
> simple download link)?
yeah you probably need to check it out with svn and build it.
you probably also need to "modprobe msr".
the BIOS workarounds for those errata amount to setting those bits (i.e.
bit 3 of MSR 0xc0010015, bit 1 of 0xc0011023 and bit 23 of 0xc0011023)
... for these specific workarounds we can tweak them dynamically. if you
execute that script i pasted you'll disable the workarounds... which
will make your B2 behave like a B3.
-dean
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Math-atlas-devel mailing list
Math-atlas-devel@...
https://lists.sourceforge.net/lists/listinfo/math-atlas-devel
« Return to Thread: k10h post-BIOS patch effects
| Free embeddable forum powered by Nabble | Forum Help |
