From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: KSM with Debian GNU/Linux Date: Mon, 09 Aug 2010 15:30:38 +0400 Message-ID: <4C5FE6DE.40108@msgid.tls.msk.ru> References: <20100809101635.GB1771@defiant.freesoftware> <4C5FD800.9000905@msgid.tls.msk.ru> <20100809110049.GC30078@develbox.linuxbox.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: dbareiro@gmx.net, KVM General , nikola.ciprich@linuxbox.cz To: Nikola Ciprich Return-path: Received: from isrv.corpit.ru ([86.62.121.231]:49500 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756133Ab0HILao (ORCPT ); Mon, 9 Aug 2010 07:30:44 -0400 In-Reply-To: <20100809110049.GC30078@develbox.linuxbox.cz> Sender: kvm-owner@vger.kernel.org List-ID: 09.08.2010 15:00, Nikola Ciprich =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Hi, > I don't have clue what glibc is contained in debian, but it seems > to me that at least compile-time KSM support DOES depend on glibc. > I'm using RHEL5-based system and KSM support doesn't get compiled in > by default. =46or KSM to be compiled in, one need to have kernel headers of the corresponding system interface (madvise() system call). That is not part of glibc (even while madvise function is declared by glibc) but part of kernel headers which glibc uses itself during compilation. In debian that comes in linux-libc-dev package, some other distribution may bundle it together with glibc but that's pure packaging stuff, these headers does not come from glibc sources. > But since I use new kernel, I add following to CFLAGS while compiling > qemu-kvm and then it works: > -DMADV_MERGEABLE=3D12 -DMADV_UNMERGEABLE=3D13 This is what the patch in debian package does, to get KSM-ready binary even without recent-enough kernel headers (like on Lenny). /mjt