[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Allow the backward time syncing in domU.


  • To: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Yi, Shunli" <syi@xxxxxxxxxxxx>
  • Date: Fri, 8 Oct 2010 02:59:05 -0700
  • Accept-language: zh-CN, en-US
  • Acceptlanguage: zh-CN, en-US
  • Delivery-date: Fri, 08 Oct 2010 03:03:55 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Actmz2POhROB5Sk3SLSUqI/EpBWwcA==
  • Thread-topic: Allow the backward time syncing in domU.

Hi:

When we use dependent clock in domU, the time syncing from Dom0 to DomU is monotonic (in xenified kernel 2.6.28.8 ).

 

While, when I read the source code of arch/i386/time-xen.c, I think we can allow the backward time syncing by reset the monotonic time value (monotonic.tv) when the HYPERVISOR_shared_info->wc_version is changed.

 

I’ve tested that, whenever the Dom0 time changed, the domU’s time would be sync-ed immediately. (with /proc/sys/xen/independent_wallclock=0 ).

So, seems it works perfect, it’s a real dependent wall clock now.

 

It’s easy to implement the backward time syncing.

So, I wonder that, are there some risks to allow the backward time syncing?

If there isn’t known risk, I’d like to send a patch to allow the backward time syncing.

 

Could you anybody can help to understand the risks?

 

Any input is appreciated.

 

 

-Shunli

 

 



Protected by Websense Hosted Email Security — www.websense.com

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.