[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090507134813.GO28398@elte.hu>
Date: Thu, 7 May 2009 15:48:13 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Peter Oberparleiter <oberpar@...ux.vnet.ibm.com>
Cc: linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Andi Kleen <andi@...stfloor.org>,
Huang Ying <ying.huang@...el.com>, Li Wei <W.Li@....COM>,
Michael Ellerman <michaele@....ibm.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Sam Ravnborg <sam@...nborg.org>, Jeff Dike <jdike@...toit.com>
Subject: Re: [PATCH 1/4] kernel: constructor support
* Peter Oberparleiter <oberpar@...ux.vnet.ibm.com> wrote:
> Ingo Molnar wrote:
>> * Peter Oberparleiter <oberpar@...ux.vnet.ibm.com> wrote:
>>
>>> Disable constructor support for usermode Linux to prevent conflicts
>>> with host glibc.
>>
>>> +++ linux-2.6.30-rc4/init/Kconfig
>>> @@ -16,6 +16,11 @@ config DEFCONFIG_LIST
>>> default "$ARCH_DEFCONFIG"
>>> default "arch/$ARCH/defconfig"
>>> +config CONSTRUCTORS
>>> + bool
>>> + depends on !UML
>>> + default y
>>> +
>>> menu "General setup"
>>
>> Hm, excluding UML like that is sad. Is there no better solution?
>
> UML is excluded because in that environment constructors are
> called by the host glibc, so there is no need for kernel support
> on UML (in fact it would break things).
>
> Or were you referring to the actual way the exclusion is
> implemented?
the way it's done is OK (there's really just UML in this situation),
but the question is really, shouldnt it be possible to coverage-test
UML instances 'from the inside'?
Plus, if any other kernel facility grows out of this or makes use of
it, UML will be left out in the cold.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists