All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: George Washington Dunlap III <dunlapg@umich.edu>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Re: Is continuous replication of state possible?
Date: Mon, 10 Jan 2005 18:22:21 -0800	[thread overview]
Message-ID: <41E3385D.2090906@diku.dk> (raw)
In-Reply-To: <Pine.LNX.4.60.0501101137400.11559@stclair.eecs.umich.edu>

George Washington Dunlap III wrote:

> The main trick is that there are several different counters you could 
> use. The one spoken of mainly in the literature is the instruction 
> counter (which, on both Athlons and P4's is unusable).  However, there 
> are repeatable branch counters on both platforms.  Logging the
> <eip, branch_count> tuple at every interrupt allows us to re-deliver the 
> interrupts precisely.  (See Mellor-Crummey89 for a software version of 
> this same idea.)
> 
> Maybe sometime I'll post a whitepaper about the dirty details of doing 
> deterministic replay on P4's and Athlons.  If you're interested, I have 
> an e-mail that I've already sent to several people (including the Xen 
> team) with the details.

I'd like to see a copy of that email, thanks.

Jacob


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

      reply	other threads:[~2005-01-11  2:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050109030704.8BAB689DA7@sc8-sf-spam1.sourceforge.net>
2005-01-10 16:53 ` Is continuous replication of state possible? George Washington Dunlap III
2005-01-11  2:22   ` Jacob Gorm Hansen [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=41E3385D.2090906@diku.dk \
    --to=jacobg@diku.dk \
    --cc=dunlapg@umich.edu \
    --cc=xen-devel@lists.sourceforge.net \
    /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.