qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] vdso for x86_64-linux-user
Date: Wed, 24 Jul 2013 06:34:54 -1000	[thread overview]
Message-ID: <51F0022E.7010507@twiddle.net> (raw)
In-Reply-To: <CAFEAcA9=-bN7b=sQR3oHbQfoPsJjJd5B9conRp_bbwybQmLBoQ@mail.gmail.com>

On 07/23/2013 11:15 AM, Peter Maydell wrote:
> On 23 July 2013 21:27, Richard Henderson <rth@twiddle.net> wrote:
>> This is a refresh of a patch I wrote in 2010, and have re-posted every
>> 6 months thereafter.  To my knowledge, it has never been reviewed.
>>
>> It supplies a replacement for the required x86-64 vdso.  Anyone trying
>> to emulate x86_64-linux on a host other than same will quickly run into
>> the lack of a gettimeofday syscall, which glibc assumes is always
>> provided by the vdso.
> 
> Do we really need to mess with building an x86 shared object
> and pulling it in, rather than the kind of ad-hoc way we
> handle the ARM commpage?

Isn't the arm ad-hoc really the much larger and uglier hack?


r~

  reply	other threads:[~2013-07-24 16:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 20:27 [Qemu-devel] [PATCH 0/2] vdso for x86_64-linux-user Richard Henderson
2013-07-23 20:27 ` [Qemu-devel] [PATCH 1/2] linux-user: Build vdso for x64 Richard Henderson
2013-07-23 20:27 ` [Qemu-devel] [PATCH 2/2] linux-user: Load a VDSO for x86-64 Richard Henderson
2013-07-23 21:15 ` [Qemu-devel] [PATCH 0/2] vdso for x86_64-linux-user Peter Maydell
2013-07-24 16:34   ` Richard Henderson [this message]
2013-07-24 16:39     ` Peter Maydell
2013-07-24 17:37       ` Richard Henderson

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=51F0022E.7010507@twiddle.net \
    --to=rth@twiddle.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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).