All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [Xen-changelog] Indirect	hypercalls	through	ahypercall transfer page.
Date: Wed, 08 Feb 2006 17:15:17 -0800	[thread overview]
Message-ID: <43EA97A5.4020208@redhat.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D40A60A@liverpoolst.ad.cl.cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]

Ian Pratt wrote:

> The vsyscall
> page lives within the fixaddr region, and its virtual address needs to
> be known at *compile* time as it gets built into various elf objects.

That's not necessarily the case.

The FC x86 kernel has random vdso address support.  I don't know why
this isn't also enabled for x86-64 but there is no real reason for that.
   These are, after all, DSOs which need little fixup for a new location.

-- 
➧ 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

  reply	other threads:[~2006-02-09  1:15 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 [this message]
2006-02-09  1:21   ` Ulrich Drepper
  -- 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=43EA97A5.4020208@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.