From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Why disable vdso by default with CONFIG_PARAVIRT?
Date: Tue, 12 Dec 2006 12:11:46 -0800 [thread overview]
Message-ID: <457F0D02.3040000@goop.org> (raw)
In-Reply-To: <200612121301.08444.ak@suse.de>
Andi Kleen wrote:
> I don't think being incompatible to old binaries is a sensible default. That
> is why I changed the wrong default. If paravirt ops cannot supply
> a compatible vdso it has to do without one.
Do you know what glibc2.1 actually needs from the vdso? Does it
actually interpret as an elf file, or just it just jump into it to
perform syscalls? I wonder if we could use a fault in the vdso memory
range to act as a syscall, or something like that?
J
next prev parent reply other threads:[~2006-12-12 20:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 1:22 Why disable vdso by default with CONFIG_PARAVIRT? Jeremy Fitzhardinge
2006-12-12 1:42 ` Zachary Amsden
2006-12-12 1:44 ` Jeremy Fitzhardinge
2006-12-12 1:46 ` Zachary Amsden
2006-12-12 1:49 ` Jeremy Fitzhardinge
2006-12-12 3:02 ` Andi Kleen
2006-12-12 6:28 ` Zachary Amsden
2006-12-12 6:50 ` Jeremy Fitzhardinge
2006-12-12 7:27 ` Andi Kleen
2006-12-12 10:23 ` Jeremy Fitzhardinge
2006-12-12 12:01 ` Andi Kleen
2006-12-12 20:11 ` Jeremy Fitzhardinge [this message]
2006-12-12 21:15 ` Andi Kleen
2006-12-13 2:04 ` Rusty Russell
2006-12-13 4:36 ` Rusty Russell
2006-12-13 5:25 ` Rusty Russell
2006-12-12 23:22 ` Rusty Russell
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=457F0D02.3040000@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).