Alex:
Can't exposing an formula cooperatively between domain
hypervisor solve the prpblem?
E.g: guest_ITC=host_ITC * fact + offset;If the host ITC is
accurate enough.
Or guest_ITC = host_high_precise_timer_count * fat + offset; if
the hyprevisor want to use other
On Tue, 2006-02-14 at 18:10 +0800, Dong, Eddie wrote:
Alex:
Can't exposing an formula cooperatively between domain
hypervisor solve the prpblem?
E.g: guest_ITC=host_ITC * fact + offset;If the host ITC is
accurate enough.
Or guest_ITC = host_high_precise_timer_count *
... Of course, our automated tests only currently test x86
32/32p/64 xen. We should fix this and add ia64 (we now have a
couple of
machines). It's on the (long) todo list.
Ian
Does anyone in the Xen/ia64 community have an employee or
contractor located in Cambridge that could assist with
Base on my understanding, the ITC drift between different processor
after fixup done in Linux or Xen today is less than 100ns. So I think
that is not a big issue as if we guarantee the guest doesn't see
backward time.
The context switch time of Xen or Linux doesn't matter. The worst case
Hi,
I tested Page reference counter.
I had a problem which DomU have a General Exception
at DomU's booting time.
I fixed Reserved Register/Field fault in printf().
This bug is probably occurred by wrong type arguments in sal_emulate().
This bug was very difficult.
I checked compile warnnigs,
Hi,
This is wrong type cast.
This patch fix warnning of incompatible pointer type.
Signed-off-by: Akio Takebe [EMAIL PROTECTED]
diff -r 982b9678af2c xen/arch/ia64/xen/hypercall.c
--- a/xen/arch/ia64/xen/hypercall.c Fri Feb 10 23:16:33 2006
+++ b/xen/arch/ia64/xen/hypercall.c Wed Feb 15
Hi,
I'm making a patch for domain destruction.
While I tested my patch by repeatedly
creating/destructing domains,
a reserved register/field fault occurred in load_region_regs().
The cause of this fault is rr0 value overflow(0x)
because metaphysical_rr0 in the arch_domain struct
