From: Jakub Jelinek <jakub@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: smaller kernel with no real time futexes
Date: Wed, 1 Aug 2007 19:10:43 -0400 [thread overview]
Message-ID: <20070801231043.GP2063@devserv.devel.redhat.com> (raw)
In-Reply-To: <200708012124.34341.ak@suse.de>
On Wed, Aug 01, 2007 at 09:24:34PM +0200, Andi Kleen wrote:
> Adrian,
>
> You said earlier you're looking at smaller allnoconfig kernels.
> One thing I noticed recently that realtime pi futexes are always
> enabled and that pulls in a lot of other code (like the plists)
>
> Userland needs to handle them not being available anyways for older
> kernels.
>
> Might be worth looking into turning that into a CONFIG.
That's a very bad idea. glibc configured for 2.6.18 and higher kernels
assumes PI futexes are present.
Jakub
prev parent reply other threads:[~2007-08-01 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 19:24 smaller kernel with no real time futexes Andi Kleen
2007-08-01 23:10 ` Jakub Jelinek [this message]
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=20070801231043.GP2063@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=ak@suse.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.