* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > VDSO is only a problem if (1) the hypervisor wants to reserve the
> > top virtual address space (CONFIG_PARAVIRT=y), and (2) the glibc is
> > old and
>
> It broke the boot even with native hardware, no hypervisor
yeah - i just sent the fix for that regression - by making
CONFIG_COMPAT_VDSO usable again.
basically, we want to avoid all the compatibility mess that exists on
the hypervisor side to enter the Linux kernel.
Ingo
-
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/
