From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Chris Wright <chrisw@sous-sol.org>,
Linus Torvalds <torvalds@osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Jan Beulich <jbeulich@novell.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT
Date: Fri, 16 Mar 2007 09:33:42 -0700 [thread overview]
Message-ID: <45FAC6E6.5090000@goop.org> (raw)
In-Reply-To: <20070316163118.GA12999@elte.hu>
Ingo Molnar wrote:
> that's what is the case right now, but much of the intention behind the
> vma based vDSO is to enable per-process randomized vdso locations, and
> various distributions do that. So the 'modern' vDSO concept is very much
> relocatable.
No, the point is that it never needs relocating. The kernel can map it
anywhere and userspace can cope. Its only the broken glibcs which
require relocation.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Zachary Amsden <zach@vmware.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Beulich <jbeulich@novell.com>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@suse.de>,
Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: [RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT
Date: Fri, 16 Mar 2007 09:33:42 -0700 [thread overview]
Message-ID: <45FAC6E6.5090000@goop.org> (raw)
In-Reply-To: <20070316163118.GA12999@elte.hu>
Ingo Molnar wrote:
> that's what is the case right now, but much of the intention behind the
> vma based vDSO is to enable per-process randomized vdso locations, and
> various distributions do that. So the 'modern' vDSO concept is very much
> relocatable.
No, the point is that it never needs relocating. The kernel can map it
anywhere and userspace can cope. Its only the broken glibcs which
require relocation.
J
next prev parent reply other threads:[~2007-03-16 16:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 2:47 [RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT Zachary Amsden
2007-03-16 3:20 ` Jeremy Fitzhardinge
2007-03-16 3:20 ` Jeremy Fitzhardinge
2007-03-16 4:03 ` Zachary Amsden
2007-03-16 4:03 ` Zachary Amsden
2007-03-16 5:10 ` Jeremy Fitzhardinge
2007-03-16 5:58 ` Zachary Amsden
2007-03-16 5:58 ` Zachary Amsden
2007-03-16 8:08 ` Jan Beulich
2007-03-16 8:41 ` Zachary Amsden
2007-03-16 16:46 ` Jeremy Fitzhardinge
2007-03-16 17:09 ` Jan Beulich
2007-03-16 23:09 ` Jan Engelhardt
2007-03-16 11:56 ` Eric W. Biederman
2007-03-16 11:56 ` Eric W. Biederman
2007-03-16 16:25 ` Jeremy Fitzhardinge
2007-03-16 16:25 ` Jeremy Fitzhardinge
2007-03-16 16:31 ` Ingo Molnar
2007-03-16 16:33 ` Jeremy Fitzhardinge [this message]
2007-03-16 16:33 ` Jeremy Fitzhardinge
2007-03-16 19:06 ` Eric W. Biederman
2007-03-16 19:06 ` Eric W. Biederman
2007-03-16 19:46 ` Jeremy Fitzhardinge
2007-03-16 19:38 ` Zachary Amsden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FAC6E6.5090000@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=ebiederm@xmission.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.