Displaying 2 results from an estimated 2 matches for "snar".
Did you mean:
star
2007 Apr 18
3
[patch] paravirt: VDSO page is essential
...does not
> handle the VDSO properly then it can work things around via the vdso=0
> boot option. Or CONFIG_PARAVIRT should not have been merged. But in any
> case, it is a basic taste issue: we DO NOT #ifdef around core features
> like this!)
I agree with the criticism, dislike the snarly comments, and disagree
with this patch.
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
can't handle a VDSO mapped anywhere but 0xFFFFE000
(CONFIG_COMPAT_VDSO=y).
Now, KVM wants to use CONFIG_PARAV...
2007 Apr 18
3
[patch] paravirt: VDSO page is essential
...does not
> handle the VDSO properly then it can work things around via the vdso=0
> boot option. Or CONFIG_PARAVIRT should not have been merged. But in any
> case, it is a basic taste issue: we DO NOT #ifdef around core features
> like this!)
I agree with the criticism, dislike the snarly comments, and disagree
with this patch.
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
can't handle a VDSO mapped anywhere but 0xFFFFE000
(CONFIG_COMPAT_VDSO=y).
Now, KVM wants to use CONFIG_PARAV...