qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Re: amd64 compile
Date: Sun, 25 Apr 2004 20:52:52 +0200	[thread overview]
Message-ID: <1082919171.14634.20.camel@rapid> (raw)
In-Reply-To: <5294495.u1jPGWrt4o@schnecke2.gabrielebner.at>

[-- Attachment #1: Type: text/plain, Size: 319 bytes --]

On Sun, 2004-04-25 at 20:38, Gabriel Ebner wrote:
> Hello,
> 
> J. Mayer wrote:
> > I added 3 attachements to my message. The one concerning
> > cpu_get_real_ticks is named ticks.diff
> 
> That one's empty

Oops, you're aboslutely right, I'm sorry... Here it is again.

-- 
J. Mayer <l_indien@magic.fr>
Never organized

[-- Attachment #2: ticks.diff --]
[-- Type: text/x-patch, Size: 574 bytes --]

Index: vl.c
===================================================================
RCS file: /cvsroot/qemu/qemu/vl.c,v
retrieving revision 1.59
diff -u -r1.59 vl.c
--- vl.c        12 Apr 2004 20:39:28 -0000      1.59
+++ vl.c        19 Apr 2004 13:04:29 -0000
@@ -358,7 +358,20 @@
     return val;
 }
 
+#elif defined(__x86_64__)
+
+int64_t cpu_get_real_ticks(void)
+{
+    uint32_t low,high;
+    int64_t val;
+    asm volatile("rdtsc" : "=a" (low), "=d" (high));
+    val = high;
+    val <<= 32;
+    val |= low;
+    return val;
+}
+
 #else
 #error unsupported CPU
 #endif

      reply	other threads:[~2004-04-25 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-25 15:32 [Qemu-devel] amd64 compile Martin Garton
2004-04-25 16:07 ` J. Mayer
2004-04-25 16:23   ` Martin Garton
2004-04-25 18:20     ` J. Mayer
2004-04-25 18:40       ` J. Mayer
2004-04-25 19:02         ` Fabrice Bellard
2004-04-25 19:46           ` J. Mayer
2004-04-25 17:46   ` [Qemu-devel] " Gabriel Ebner
2004-04-25 18:09     ` J. Mayer
2004-04-25 18:38       ` [Qemu-devel] " Gabriel Ebner
2004-04-25 18:52         ` J. Mayer [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=1082919171.14634.20.camel@rapid \
    --to=l_indien@magic.fr \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).