All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [RFC] PATCH 0/4 - Time virtualization
Date: Wed, 26 Apr 2006 14:01:10 -0400	[thread overview]
Message-ID: <20060426180110.GB8142@ccure.user-mode-linux.org> (raw)
In-Reply-To: <m1d5feotur.fsf@ebiederm.dsl.xmission.com>

On Wed, Apr 19, 2006 at 02:25:00AM -0600, Eric W. Biederman wrote:
> That patch should probably be separated, from the rest.
> But it looks like a fairly sane idea. 

Yeah, I'll keep these together for now, but the ptrace one is
conceptually different from the rest.

> I think you missed a couple essential things to a time namespace.
> Timers.  The posix timers, in particular.  The worst
> of those is the monotonic timer.  

Oops, thanks for pointing that out.

> In the case of migration the ugly case to properly handle is the
> monotonic timer.   That needs an offset yet it is absolutely forbidden
> to provide that offset from the inside.  So this is the one namespace
> that I think is inappropriate to use sys_unshare to create.
> We need a system call so that we can specify the minimum or the
> starting monotonic time base.

For migration, it looks like the container will have to specify the
time base at creation so that everything in it will have a consistent
view of time if they get moved around.

So, maybe it belongs in clone as a "backwards" flag similar to
CLONE_NEWNS.

				Jeff


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Dike <jdike@addtoit.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [RFC] PATCH 0/4 - Time virtualization
Date: Wed, 26 Apr 2006 14:01:10 -0400	[thread overview]
Message-ID: <20060426180110.GB8142@ccure.user-mode-linux.org> (raw)
In-Reply-To: <m1d5feotur.fsf@ebiederm.dsl.xmission.com>

On Wed, Apr 19, 2006 at 02:25:00AM -0600, Eric W. Biederman wrote:
> That patch should probably be separated, from the rest.
> But it looks like a fairly sane idea. 

Yeah, I'll keep these together for now, but the ptrace one is
conceptually different from the rest.

> I think you missed a couple essential things to a time namespace.
> Timers.  The posix timers, in particular.  The worst
> of those is the monotonic timer.  

Oops, thanks for pointing that out.

> In the case of migration the ugly case to properly handle is the
> monotonic timer.   That needs an offset yet it is absolutely forbidden
> to provide that offset from the inside.  So this is the one namespace
> that I think is inappropriate to use sys_unshare to create.
> We need a system call so that we can specify the minimum or the
> starting monotonic time base.

For migration, it looks like the container will have to specify the
time base at creation so that everything in it will have a consistent
view of time if they get moved around.

So, maybe it belongs in clone as a "backwards" flag similar to
CLONE_NEWNS.

				Jeff

  reply	other threads:[~2006-04-26 19:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 17:19 [uml-devel] [RFC] PATCH 0/4 - Time virtualization Jeff Dike
2006-04-13 17:19 ` Jeff Dike
2006-04-14  0:31 ` [uml-devel] " john stultz
2006-04-14  0:31   ` john stultz
2006-04-14  1:53   ` [uml-devel] " Jeff Dike
2006-04-14  1:53     ` Jeff Dike
2006-04-14 16:24     ` john stultz
2006-04-14 16:24       ` john stultz
2006-04-19  8:25 ` Eric W. Biederman
2006-04-19  8:25   ` Eric W. Biederman
2006-04-26 18:01   ` Jeff Dike [this message]
2006-04-26 18:01     ` Jeff Dike
2006-04-28 11:33     ` [uml-devel] " Blaisorblade
2006-04-28 11:33       ` Blaisorblade
2006-04-28 11:48       ` Jeff Dike
2006-04-28 11:48         ` Jeff Dike
2006-04-28 12:14         ` Jeff Dike
2006-04-28 12:14           ` Jeff Dike
2006-04-28 13:54         ` Blaisorblade
2006-04-28 13:54           ` Blaisorblade
2006-04-28 15:15           ` Jeff Dike
2006-04-28 15:15             ` Jeff Dike
2006-04-28 20:10             ` Blaisorblade
2006-04-28 20:10               ` Blaisorblade
2006-04-28 16:18           ` Eric W. Biederman
2006-04-28 16:18             ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2006-04-14 15:39 Brock, Anthony - NET
2006-04-14 15:33 ` Jeff Dike

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=20060426180110.GB8142@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.