From: Ulrich Drepper <drepper@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: Re: [Xen-changelog] Indirect hypercalls through ahypercall transfer page.
Date: Wed, 08 Feb 2006 17:21:18 -0800 [thread overview]
Message-ID: <43EA990E.5000807@redhat.com> (raw)
In-Reply-To: <43EA97A5.4020208@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 756 bytes --]
Ulrich Drepper wrote:
> I don't know why
> this isn't also enabled for x86-64 but there is no real reason for that.
Actually, I remember. It's Andi insistance on this stupid vsyscall
interface with fixed addresses. This is absolutely unnecessary. vdsos
are so much nicer to handle, need no special code. If somebody would
finally be able to replace the vsyscall stuff x86-64 currently uses with
a vdso implementation (passing up the address in the auxiliary vector)
all would be nice and easy. x86 and ppc already use the vdso, it's not
an unproven concept. ppc even uses it in a way which would be needed to
implement the fast gettimeofday etc.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-02-09 1:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 0:02 Re: [Xen-changelog] Indirect hypercalls through ahypercall transfer page Ian Pratt
2006-02-09 1:15 ` Ulrich Drepper
2006-02-09 1:21 ` Ulrich Drepper [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-08 16:22 Ian Pratt
2006-02-08 17:04 ` Mike D. Day
2006-02-08 9:59 Ian Pratt
2006-02-08 15:46 ` Mike D. Day
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=43EA990E.5000807@redhat.com \
--to=drepper@redhat.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.