Re: [PATCH 000/208] big x86 FPU code rewrite

2015-07-17 Thread Andy Lutomirski
On Tue, May 5, 2015 at 10:50 AM, Ingo Molnar wrote: > > * Linus Torvalds wrote: > >> On Tue, May 5, 2015 at 9:23 AM, Ingo Molnar wrote: >> > 83 files changed, 3742 insertions(+), 2841 deletions(-) >> >> How much of this is just the added instrumentation? [...] > > Half of it is that, plus a lot

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-29 Thread Ingo Molnar
* Dave Hansen wrote: > Hey Ingo, > > This throws a warning if I try to run one of my MPX programs: > > > [ 22.907739] [ cut here ] > > [ 22.907776] WARNING: CPU: 0 PID: 500 at > > /home/davehans/linux.git/arch/x86/kernel/fpu/core.c:324 > > fpu__activate_stopped+0x

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-26 Thread Bobby Powers
Hello, Ingo Molnar wrote: > Please have a look. I've been running this for ~ 2 weeks. I've only seen one issue, when emerging mesa 10.5.6: [May26 20:41] traps: aclocal-1.15[27452] trap invalid opcode ip:7f6331031ab0 sp:7ffe73ece880 error:0 in libperl.so.5.20.2[7f6330f18000+19e000] [ +0.51

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-19 Thread Ingo Molnar
* Ingo Molnar wrote: > [Second part of the series - Gmail didn't like me sending so many mails.] Just a quick update: I merged these patches to -rc4 (sans the benchmarking bits, which still need more work) and applied them to tip:x86/fpu and have pushed them out, so that it gets more testing,

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-12 Thread Dave Hansen
Hey Ingo, This throws a warning if I try to run one of my MPX programs: > [ 22.907739] [ cut here ] > [ 22.907776] WARNING: CPU: 0 PID: 500 at > /home/davehans/linux.git/arch/x86/kernel/fpu/core.c:324 > fpu__activate_stopped+0x87/0x90() > [ 22.907836] Modules linke

[PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Ingo Molnar
[Second part of the series - Gmail didn't like me sending so many mails.] Over the past 10 years the x86 FPU has organically grown into somewhat of a spaghetti monster that few (if any) kernel developers understand and which code few people enjoy to hack. Many people suggested over the years that

[PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Ingo Molnar
[Second part of the series - Gmail didn't like me sending so many mails.] Over the past 10 years the x86 FPU has organically grown into somewhat of a spaghetti monster that few (if any) kernel developers understand and which code few people enjoy to hack. Many people suggested over the years that

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Ingo Molnar
* Linus Torvalds wrote: > On Tue, May 5, 2015 at 9:23 AM, Ingo Molnar wrote: > > 83 files changed, 3742 insertions(+), 2841 deletions(-) > > How much of this is just the added instrumentation? [...] Half of it is that, plus a lot of comments. > [...] Because that's almost a thousand new lin

Re: [PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Linus Torvalds
On Tue, May 5, 2015 at 9:23 AM, Ingo Molnar wrote: > 83 files changed, 3742 insertions(+), 2841 deletions(-) How much of this is just the added instrumentation? Because that's almost a thousand new lines, which makes me unhappy. The *last* thing we want is to make this thing bigger. I'm not conv

[PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Ingo Molnar
[Take #2 - sorry!] Over the past 10 years the x86 FPU has organically grown into somewhat of a spaghetti monster that few (if any) kernel developers understand and which code few people enjoy to hack. Many people suggested over the years that it needs a major cleanup, and some time ago I went "wh

[PATCH 000/208] big x86 FPU code rewrite

2015-05-05 Thread Ingo Molnar
Over the past 10 years the x86 FPU has organically grown into somewhat of a spaghetti monster that few (if any) kernel developers understand and which code few people enjoy to hack. Many people suggested over the years that it needs a major cleanup, and some time ago I went "what the heck" and sta