From: Andrew Lutomirski <luto@mit.edu>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT pull] x86 vdso updates
Date: Fri, 27 May 2011 11:05:51 -0400 [thread overview]
Message-ID: <BANLkTimdne9WVDfooOGcVDtAaG=G4T7uTA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTindgVfP530GDGvonp7iXE=hW833gg@mail.gmail.com>
On Fri, May 27, 2011 at 10:59 AM, richard -rw- weinberger
<richard.weinberger@gmail.com> wrote:
> On Fri, May 27, 2011 at 2:10 PM, Andrew Lutomirski <luto@mit.edu> wrote:
>> On Fri, May 27, 2011 at 7:59 AM, richard -rw- weinberger
>> If this is considered enough of a regression, then I guess we can
>> leave vsyscall64 around for awhile, but it will require extra work in
>> the soon-to-be syscall emulation hack to make sure that UML can still
>> trap the syscall.
>
> As long the time within UML is synchronous with the host everything is
> fine, right?
I think so. I haven't used UML in a long time.
> So, as _last_ choice we could disable the ability to change the time within UML.
>
> IMHO it's not a big deal when getcpu() returns a wrong CPU layout on UML.
>
>> The real solution is to fix glibc to use the vDSO which should avoid
>> this problem entirely.
>
> Is this "bug" known? And the biggest question, will Ulrich fix it some day?
I added the bit about UML to
http://sourceware.org/bugzilla/show_bug.cgi?id=12813. I don't know
what Ulrich will do.
--Andy
next prev parent reply other threads:[~2011-05-27 15:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 18:50 Thomas Gleixner
2011-05-26 21:26 ` Andy Lutomirski
2011-05-27 6:12 ` Ingo Molnar
2011-05-27 11:36 ` Andrew Lutomirski
2011-05-27 11:59 ` richard -rw- weinberger
2011-05-27 12:10 ` Andrew Lutomirski
2011-05-27 14:59 ` richard -rw- weinberger
2011-05-27 15:05 ` Andrew Lutomirski [this message]
2011-05-29 9:51 ` richard -rw- weinberger
2011-05-29 14:57 ` Andrew Lutomirski
2011-05-29 15:10 ` richard -rw- weinberger
2011-05-29 15:28 ` Andrew Lutomirski
2011-05-29 16:40 ` richard -rw- weinberger
2011-05-27 14:54 ` Andrew Lutomirski
2011-05-28 15:35 ` Ingo Molnar
2011-05-29 1:41 ` Andrew Lutomirski
2011-05-29 14:39 ` Mikael Pettersson
2011-05-29 14:59 ` Andrew Lutomirski
2011-05-29 16:01 ` Mikael Pettersson
2011-05-29 16:35 ` Andrew Lutomirski
2011-05-29 18:06 ` Mikael Pettersson
2011-05-29 18:44 ` Andrew Lutomirski
2011-05-30 3:26 ` Andrew Lutomirski
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='BANLkTimdne9WVDfooOGcVDtAaG=G4T7uTA@mail.gmail.com' \
--to=luto@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=richard.weinberger@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®