On Thu, Apr 13, 2006 at 05:31:27PM -0700, john stultz wrote:
> Looks interesting. I've never quite understood the need for different
> time domains, it only allows you to run one domain with the incorrect
> time, but I'm sure there is some use case that is desired.
There are a few possible answers -
If when this virtualization stuff is done, no one has done anything with
time, someone is going to moan.
Once in a while, you want to fiddle your system clock to make sure that
a cron job or something does what it's supposed to.
There was some extra infrastructure that UML needed in order to start using
this stuff, so I chose a fairly simple virtualization case to accompany it.
> I'm not psyched about possible namespace vs nanosecond confusion w/
> terms like "time_ns", but that's pretty minor.
Yeah, names can be changed.
> Also I hope you're not wanting to deal w/ NTP adjustments between
> domains that have the incorrect time? That would be very ugly.
No, the domain stores an offset from the system time, so it automatically
gets the system's NTP adjustments.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
