From: tupeng212 <tupeng212@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>, Tim Deegan <tim@xen.org>,
Keir Fraser <keir@xen.org>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH, RFC v2] x86/HVM: assorted RTC emulation adjustments (was Re: Big Bug:Time in VM goes slower...)
Date: Thu, 16 Aug 2012 22:27:12 +0800 [thread overview]
Message-ID: <2012081622270760996017@gmail.com> (raw)
In-Reply-To: 502D1C8A0200007800095851@nat28.tlf.novell.com
[-- Attachment #1.1: Type: text/plain, Size: 691 bytes --]
Okay, some back and forth is there in any case, but without
knowing the time distance between the individual instances it's
hard to tell whether what I'm thinking of might help.
> besides, I checked my former simple tester this morning after it ran for a
> whole night, it lagged much.
Could you btw quantify the lagging?
// I didn't pay attention to it, but about half an hour's lagging certainly exist.
when you will go home, you can also have a try to see result tomorrow morning.
Your tester sets only a single, constant rate repeatedly, right? //yes, the simplest test just setting a single 10000 down repeatly.
If so, then the thought of adjustment likely won't help.
[-- Attachment #1.2: Type: text/html, Size: 1842 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-08-16 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:51 [PATCH, RFC v2] x86/HVM: assorted RTC emulation adjustments (was Re: Big Bug:Time in VM goes slower...) Jan Beulich
2012-08-15 14:07 ` tupeng212
2012-08-15 14:12 ` tupeng212
2012-08-16 8:22 ` Jan Beulich
2012-08-16 13:43 ` tupeng212
2012-08-16 14:15 ` Jan Beulich
2012-08-16 14:27 ` tupeng212 [this message]
2012-08-15 15:00 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2012081622270760996017@gmail.com \
--to=tupeng212@gmail.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.