[PATCH] x86, cyrix: add alternative Device ID of Geode GX1 SoC

2017-06-04 Thread Christian Sünkenberg
. Performance impact was verified using "openssl speed", with write-back caching scaling throughput between -3% and +41%. Signed-off-by: Christian Sünkenberg <christian.suenkenb...@student.kit.edu> --- arch/x86/kernel/cpu/cyrix.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/

[PATCH] x86, cyrix: add alternative Device ID of Geode GX1 SoC

2017-06-04 Thread Christian Sünkenberg
. Performance impact was verified using "openssl speed", with write-back caching scaling throughput between -3% and +41%. Signed-off-by: Christian Sünkenberg --- arch/x86/kernel/cpu/cyrix.c | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/x86/kernel/cpu/cyrix.c b/arch/x86/kernel/cpu/

Re: [Bisected] 3.7-rc1 can't resume (still present in 3.9)

2013-07-12 Thread Christian Sünkenberg
Hello, On 07/11/2013 01:57 AM, H. Peter Anvin wrote: > On 07/10/2013 01:52 PM, Christian Sünkenberg wrote: >> Hello, >> >> On 05/01/2013 07:33 PM, H. Peter Anvin wrote: >>> On 05/01/2013 10:01 AM, Jonas Heinrich wrote: >>>> Hello, I tried the new

Re: [Bisected] 3.7-rc1 can't resume (still present in 3.9)

2013-07-12 Thread Christian Sünkenberg
Hello, On 07/11/2013 01:57 AM, H. Peter Anvin wrote: On 07/10/2013 01:52 PM, Christian Sünkenberg wrote: Hello, On 05/01/2013 07:33 PM, H. Peter Anvin wrote: On 05/01/2013 10:01 AM, Jonas Heinrich wrote: Hello, I tried the newest kernel, 3.9 today but the bug is still present. Applying

Re: [Bisected] 3.7-rc1 can't resume (still present in 3.9)

2013-07-10 Thread Christian Sünkenberg
Hello, On 05/01/2013 07:33 PM, H. Peter Anvin wrote: > On 05/01/2013 10:01 AM, Jonas Heinrich wrote: >> Hello, I tried the newest kernel, 3.9 today but the bug is still >> present. Applying the attached patch solves the bug for me. >> >> Best regards, Jonas Heinrich > > Okay... WTF is going on

Re: [Bisected] 3.7-rc1 can't resume (still present in 3.9)

2013-07-10 Thread Christian Sünkenberg
Hello, On 05/01/2013 07:33 PM, H. Peter Anvin wrote: On 05/01/2013 10:01 AM, Jonas Heinrich wrote: Hello, I tried the newest kernel, 3.9 today but the bug is still present. Applying the attached patch solves the bug for me. Best regards, Jonas Heinrich Okay... WTF is going on here? Does