From: Dave Winchell <dwinchell@virtualiron.com>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ben Guthro <bguthro@virtualiron.com>
Subject: Re: [PATCH 1/2] Migrate tsc values during migration
Date: Fri, 06 Jun 2008 10:49:45 -0400 [thread overview]
Message-ID: <48494E89.5070200@virtualiron.com> (raw)
In-Reply-To: <FE7BBCFBB500984A9A7922EBC95F516E01451C6E@pdsmsx414.ccr.corp.intel.com>
Dexuan,
Thanks for catching this. How about this (taken from msr.h)?
#if defined(__i386__)
#define rdtscll(val) \
__asm__ __volatile__("rdtsc" : "=A" (val))
#elif defined(__x86_64__)
#define rdtscll(val) do { \
unsigned int a,d; \
asm volatile("rdtsc" : "=a" (a), "=d" (d)); \
(val) = ((unsigned long)a) | (((unsigned long)d)<<32); \
} while(0)
#endif
thanks,
Dave
Cui, Dexuan wrote:
>>diff -r f1508348ffab tools/libxc/xc_domain_restore.c
>>...
>>+#define rdtscll(val) do { \
>>+ unsigned int a,d; \
>>+ asm volatile("rdtsc" : "=a" (a), "=d" (d)); \
>>+ (val) = ((unsigned long)a) | (((unsigned long)d)<<32); \
>>+} while(0)
>>+
>> /* max mfn of the current host machine */
>> static unsigned long max_mfn;
>>...
>>
>>
>
>The "rdtscll" definition is buggy for __i386__ since sizeof "int" and "long" usually are 4 there.
>
>-- Dexuan
>
>
>-----Original Message-----
>From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Ben Guthro
>Sent: 2008年6月5日 23:00
>To: xen-devel; Dave Winchell
>Subject: [Xen-devel] [PATCH 1/2] Migrate tsc values during migration
>
>Migrate the last TSC values for more accurate timekeeping during live
>migration
>
>Signed-off-by: Dave Winchell <dwinchell@virtualiron.com>
>Signed-off-by: Ben Guthro <bguthro@virtualiron.com>
>
>
prev parent reply other threads:[~2008-06-06 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 14:59 [PATCH 1/2] Migrate tsc values during migration Ben Guthro
2008-06-06 2:42 ` Cui, Dexuan
2008-06-06 14:49 ` Dave Winchell [this message]
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=48494E89.5070200@virtualiron.com \
--to=dwinchell@virtualiron.com \
--cc=bguthro@virtualiron.com \
--cc=dexuan.cui@intel.com \
--cc=xen-devel@lists.xensource.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.