public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: dbareiro@gmx.net, KVM General <kvm@vger.kernel.org>,
	nikola.ciprich@linuxbox.cz
Subject: Re: KSM with Debian GNU/Linux
Date: Mon, 09 Aug 2010 15:30:38 +0400	[thread overview]
Message-ID: <4C5FE6DE.40108@msgid.tls.msk.ru> (raw)
In-Reply-To: <20100809110049.GC30078@develbox.linuxbox.cz>

09.08.2010 15:00, Nikola Ciprich пишет:
> 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.

For 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=12 -DMADV_UNMERGEABLE=13

This is what the patch in debian package does, to get KSM-ready binary
even without recent-enough kernel headers (like on Lenny).

/mjt

  reply	other threads:[~2010-08-09 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 10:16 KSM with Debian GNU/Linux Daniel Bareiro
2010-08-09 10:27 ` Michael Tokarev
2010-08-09 11:00   ` Nikola Ciprich
2010-08-09 11:30     ` Michael Tokarev [this message]
2010-08-09 14:39     ` Daniel Bareiro
2010-08-09 14:27   ` Daniel Bareiro
2010-08-09 15:28     ` Michael Tokarev
2010-08-13  1:05       ` Daniel Bareiro
2010-08-16  0:49         ` Daniel Bareiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C5FE6DE.40108@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=dbareiro@gmx.net \
    --cc=extmaillist@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox