Specifically this is needed for KSM support- MADV_MERGEABLE awareness was released in qemu-kvm-0.12, kernel support is 2.6.32; just need to get the headers in order for this support.
Via the headers extraction script, I've been playing around w/ a build locally- unfortunately I don't know near enough about the patching that's done in the existing builds (specifically what should be preserved under 2.6.32, what shouldn't, etc) to comment if my local attempt is successful.
Stuff seems to work at least, although I've not done a full rebuild...
Steps to Reproduce:
As a suggestion, I think the severity for this ticket should probably be changed to "Normal" rather than "Enhancement". The reason I say this is that this is a fairly significant feature that is simply unavailable without the newer headers, and there is no real workaround unless you take abnormal measures (outside of Gentoo ebuilds). My reading of the severity level guidelines tells me that "Normal" is probably appropriate.
I also want to add that, due to the nature of the situation, a lot of people could easily have a hard time knowing that this is even what they need. In other words, I expect a lot of people could soon be wondering why their KSM isn't working on Gentoo, but not understanding that it's the missing newer version of the linux-headers that is causing the problem. That, to me, adds to the urgency of this ticket as well, in addition to the reasons outlined above.
Oh, believe me.. I've been asking and everyone is giving me the runaround.
I'd really love to get my router working again.. It's been down for 4 months now.
Something new about this issue? We also want to use KSM. I just realized that KSM isn't working without newer linux-headers. I think it would be great if >=linux-headers-2.6.32 would be in ~arch. Since >=qemu-kvm-0.12 needs >=linux-headers-2.6.30 I've already unmasked it. Priority should be raised since I think I won't be the only one searching for some hours for the "bug" which causes KSM not to work under Gentoo.
Keep in mind I'm certainly not advocating this for everyone, but in the interim, if you absolutely know the headers pkg is going to only be used on a 2.6.32 system... the modification to the headers for this is 4 lines across 2 files (just adding the madvice syscall flag defines).
This is what I've done while waiting since I needed KSM now. I'd prefer to see a proper headers bump, but that does carry a fair bit of work/validation (hence why I reverted to the current 2.6.30 headers w/ a couple defines thrown in).
Just a thought.
Can I make my own linux-headers-2.6.32 file and throw it into portage instead of waiting forever for this to get resolved?
I'd give me lots less of a headache and I'd be able to get my systems up to par.
2.6.32 has been selected for "long-term" support, likely for a period of two years plus.
2.6.27 is going to be phased out over the next few months, AND, 2.6.27 will not have all backports because it is about 2 years old. QUOTE: "But, I do have to warn users of this tree, the older it gets, the less viable it becomes. Not all bugfixes are being backported..." /QUOTE
You can read Greg KH's notice on LWN here:
http://lwn.net/Articles/370236/ titled "Stable kernel tree status, January 18, 2010"
Created attachment 217465 [details, diff]
KMS patch for linux-headers-2.6.30-r1
Created attachment 217467 [details, diff]
KMS patch for glibc-2.11-r1
I've added KSM patches for latest linux-headers-2.6.30-r1 and glibc-2.11-r1
with these patches applied the KSM is working.
If someone wants the modified ebuild diffs, I can attach them too.
*** Bug 302829 has been marked as a duplicate of this bug. ***
Hi! I would like to have linux-headers-2.6.32 for linux/rfkill.h
linux-headers-2.6.32 now in the tree. Brian owes OSCON now.
OMG!!! I've been waiting a half a year for this!
TTTTT H H AAA N N K K Y Y OOO U U !!!
T H H A A NN N K K Y Y O O U U !!!
T HHHHH AAAAA N N N KKK Y O O U U !!!
T H H A A N NN K K Y O O U U
T H H A A N N K K Y OOO UUU !!!
(In reply to comment #15)
What is this? Do you not appreciate the ASCII art?;)
(yeah, I know there are better ways to say thank you.:-P)
just messing man. browse bash.org for a while and get a laugh :p.