All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Timer/clock for Linux
Date: Wed, 26 Apr 2006 15:21:07 +0100	[thread overview]
Message-ID: <200604261521.09177.paul@codesourcery.com> (raw)
In-Reply-To: <20060426130156.GA19293@mail.shareable.org>

On Wednesday 26 April 2006 14:01, Jamie Lokier wrote:
> Paul Brook wrote:
> > One solution (which is also desirable for other reasons) is to
> > implement some form of guest cycle counting based on the
> > instructions actually executed.  Then use that as the high-precision
> > timesource, and use some for of adaptive method to keep host and
> > guest clocks in sync.
>
> That's what I meant, expressed more clearly, except that I meant to
> count guest time based on the real time spent executing guest code,
> rather than counting individual instructions.  Thanks!

How do you propose doing that? It implies you have some way of interrupting 
the guest after it has executed a small amount of guest code, where "small" 
is less than the resolution+latency of host timer interrupts.

Paul

  reply	other threads:[~2006-04-26 14:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12  2:10 [Qemu-devel] [PATCH] Timer/clock for Linux Kazu
     [not found] ` <443E93A3.5060508@weilnetz.de>
2006-04-13 18:11   ` [Qemu-devel] [PATCH] Fix message in configure Stefan Weil
2006-04-24 21:41 ` [Qemu-devel] [PATCH] Timer/clock for Linux Fabrice Bellard
2006-04-25  0:16   ` Jamie Lokier
2006-04-25 21:10     ` Fabrice Bellard
2006-04-25 21:34       ` Jamie Lokier
2006-04-25 21:49         ` Paul Brook
2006-04-26 13:01           ` Jamie Lokier
2006-04-26 14:21             ` Paul Brook [this message]
2006-04-26 17:26               ` Jamie Lokier
2006-04-25 11:04   ` NyOS

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=200604261521.09177.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=jamie@shareable.org \
    --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 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.