|
|
|
|
|
|
|
|
|
|
xen-ia64-devel
RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime
Magenheimer, Dan (HP Labs Fort Collins) wrote:
>
> If you think of the "Xen ITC" as the official ITC, domain switch
> from A to B requires adding the offset of domainA to return to
> Xen ITC, then subtracting the offset of domainB to obtain domainB's
> ITC.
Without tracking last ITC, the guest time IRQ may be missed or multiple
triggered like the bug kevin fix for you 1-2 months ago.
>
> I think this works and is very simple... but as I said, this hasn't
> been tested because Linux doesn't do it.
Yes, both are not a big cake, but keeping 2 sets of code may cause
future support issues.
eddie
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization, Dong, Eddie
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization, Dong, Eddie
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization,
Dong, Eddie <=
|
|
|
|
|