lkml.org 
[lkml]   [2007]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] paravirt: VDSO page is essential
Roland McGrath wrote:
> Does the old userland compatibility you're concerned about really need the
> vdso to be at 0xfffffe000 in particular, or just need it to be at a fixed
> address that matches the phdrs inside the image? My recollection of the old
> glibc's limitation was that it expected the image's phdrs to match its load
> address. The xen kernels used to change this to 0xffffd000 or something,
> and AFAIK that was fine. If that's all that's needed, it is not so hard to
> adjust the vDSO contents at boot time (phdrs, shdrs, and symbols; no code
> contents use the absolute address). Under CONFIG_COMPAT_VDSO, it can see
> where the paravirt moved the fixmap to, and apply adjustments.
>

Jan Beulich just posted a patch to do just this - relocate the vdso's
ELF header. If that's all that's really required to keep COMPAT_VDSO
viable under PARAVIRT, then it seems like the way to go.

J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-03-05 23:05    [W:0.222 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site