Re: Why disable vdso by default with CONFIG_PARAVIRT?
- From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
- Date: Mon, 11 Dec 2006 17:44:28 -0800
Zachary Amsden wrote:
Jeremy Fitzhardinge wrote:
Hi Andi,
What problem do they cause together? There's certainly no problem with
Xen+vdso (in fact, its actually very useful so that it picks up the
right libc with Xen-friendly TLS).
Methinks the compat VDSO support got broken in the config? Paravirt +
COMPAT_VDSO are incompatible.
Yes, that's true, but I'm looking at arch/i386/kernel/sysenter.c:
#ifdef CONFIG_PARAVIRT
unsigned int __read_mostly vdso_enabled = 0;
#else
unsigned int __read_mostly vdso_enabled = 1;
#endif
I can't think of any reason why that should be necessary.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Why disable vdso by default with CONFIG_PARAVIRT?
- From: Zachary Amsden
- Re: Why disable vdso by default with CONFIG_PARAVIRT?
- References:
- Why disable vdso by default with CONFIG_PARAVIRT?
- From: Jeremy Fitzhardinge
- Re: Why disable vdso by default with CONFIG_PARAVIRT?
- From: Zachary Amsden
- Why disable vdso by default with CONFIG_PARAVIRT?
- Prev by Date: Re: Why disable vdso by default with CONFIG_PARAVIRT?
- Next by Date: Re: Why disable vdso by default with CONFIG_PARAVIRT?
- Previous by thread: Re: Why disable vdso by default with CONFIG_PARAVIRT?
- Next by thread: Re: Why disable vdso by default with CONFIG_PARAVIRT?
- Index(es):
Relevant Pages
|