tls f2621c88af Set the system clock (via Xen) in resettodr(), if domain 0. ... This has a couple of beneficial effects: 1) The TOD time will be preserved across boots, as one would expect. 2) Newly-started VMs will get the correct time according to domain 0. Previously, since we never set the time back to Xen, each VM would get the uncorrected system clock time, never even seeing any changes made since the current startup. I don't understand how XenoLinux slaves the other domain's clocks to the Xen "wall clock" time that we're setting here, so I haven't even tried. But now we can run ntpd in each domain without a huge offset at boot caused by never updating the wall clock time at all...		2004-07-16 22:36:33 +00:00
..
compile	…
conf	Add "options SYSCTL_INCLUDE_DESCR" to a lot of configs, but commented	2004-07-15 03:53:44 +00:00
i386	cleanup low-level bit mangling code	2004-06-14 13:55:52 +00:00
include	cleanup low-level bit mangling code	2004-06-14 13:55:52 +00:00
stand	Ignore errors on some rm -rf's for platforms that aren't quite	2004-06-21 18:20:08 +00:00
x86	Rework the physical<->machine memory mapping: offset physical addresses	2004-04-26 22:05:04 +00:00
xen	Set the system clock (via Xen) in resettodr(), if domain 0.	2004-07-16 22:36:33 +00:00
Makefile	``build.sh -m xen-i386 release'' now builds a release for NetBSD/xen	2004-05-12 16:56:41 +00:00