From: Pavel Emelyanov <xemul@parallels.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
aarcange@redhat.com, ak@linux.intel.com,
Stefani Seibold <stefani@seibold.net>,
x86@kernel.org, linux-kernel@vger.kernel.org, criu@openvz.org,
mingo@redhat.com, john.stultz@linaro.org, tglx@linutronix.de
Subject: Re: [CRIU] [PATCH] Add VDSO time function support for x86 32-bit kernel
Date: Fri, 14 Dec 2012 12:34:13 +0400 [thread overview]
Message-ID: <50CAE485.5020608@parallels.com> (raw)
In-Reply-To: <CALCETrX5KUiQaV7dsAFa1SYyWPjUVwh43HvbPwqPStMxqE0ctQ@mail.gmail.com>
On 12/14/2012 06:20 AM, Andy Lutomirski wrote:
> On Thu, Dec 13, 2012 at 6:18 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Wouldn't the vdso get mapped already and could be mremap()'d. If we
> really need more control I'd almost push for a device/filesystem node
> that could be mmapped the usual way.
>
> Hmm. That may work, but it'll still break ABI. I'm not sure that
> criu is stable enough yet that we should care. Criu people?
It's not yet, but we'd still appreciate the criu-friendly vdso redesign.
> (In brief summary: how annoying would it be if the vdso was no longer
> just a bunch of constant bytes that lived somewhere?)
It depends on what vdso is going to be. In the perfect case it should
a) be mremap-able to any address (or be at fixed address _forever_, but
I assume this is not feasible);
b) have entry points at fixed (or somehow movable) places.
I admit that I didn't understand your question properly, if I did,
please correct me.
Thanks,
Pavel
next prev parent reply other threads:[~2012-12-14 8:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 20:19 [PATCH] Add VDSO time function support for x86 32-bit kernel stefani
2012-12-12 23:34 ` H. Peter Anvin
2012-12-13 5:53 ` Stefani Seibold
2012-12-13 6:10 ` H. Peter Anvin
2012-12-13 6:14 ` H. Peter Anvin
2012-12-13 6:17 ` Stefani Seibold
2012-12-13 6:47 ` H. Peter Anvin
2012-12-13 7:17 ` Stefani Seibold
2012-12-13 19:32 ` Andy Lutomirski
2012-12-14 0:09 ` H. Peter Anvin
2012-12-14 0:20 ` Andy Lutomirski
2012-12-14 0:36 ` H. Peter Anvin
2012-12-14 1:32 ` H. Peter Anvin
2012-12-14 1:42 ` Andy Lutomirski
2012-12-14 1:49 ` H. Peter Anvin
2012-12-14 2:11 ` Andy Lutomirski
2012-12-14 2:18 ` H. Peter Anvin
2012-12-14 2:20 ` Andy Lutomirski
2012-12-14 8:34 ` Pavel Emelyanov [this message]
2012-12-14 18:35 ` [CRIU] " H. Peter Anvin
2012-12-14 18:44 ` Andy Lutomirski
2012-12-14 18:47 ` H. Peter Anvin
2012-12-14 20:12 ` Cyrill Gorcunov
2012-12-14 21:08 ` H. Peter Anvin
2012-12-14 21:20 ` Cyrill Gorcunov
2012-12-14 21:21 ` H. Peter Anvin
2012-12-14 21:27 ` Andy Lutomirski
2012-12-14 22:00 ` H. Peter Anvin
2012-12-14 22:25 ` Cyrill Gorcunov
2012-12-14 22:27 ` H. Peter Anvin
2012-12-14 22:43 ` Cyrill Gorcunov
2012-12-14 22:48 ` H. Peter Anvin
2012-12-14 23:48 ` John Stultz
2012-12-14 23:55 ` H. Peter Anvin
2012-12-17 9:05 ` Pavel Emelyanov
[not found] ` <fb2e871b-3e2a-4e96-9eb9-cb2dd4f66eaa@email.android! .com>
2012-12-17 15:21 ` H. Peter Anvin
2012-12-17 18:56 ` Pavel Emelyanov
2012-12-17 18:57 ` H. Peter Anvin
2012-12-14 22:46 ` H. Peter Anvin
2012-12-14 23:09 ` Stefani Seibold
2012-12-14 23:29 ` H. Peter Anvin
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=50CAE485.5020608@parallels.com \
--to=xemul@parallels.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=criu@openvz.org \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=stefani@seibold.net \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).