Why disable vdso by default with CONFIG_PARAVIRT?

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).

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
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 <[email protected]>

Prev by Date: Re: new procfs memory analysis feature
Next by Date: Re: [PATCH] Introduce jiffies_32 and related compare functions
Previous by thread: doubts about disk scheduling
Next by thread: Re: Why disable vdso by default with CONFIG_PARAVIRT?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]