All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
	"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: [RFC] [PATCH] use "reliable" tsc properly when available, but verify
Date: Tue, 29 Sep 2009 20:03:15 +0100	[thread overview]
Message-ID: <C6E81883.160CD%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <319577be-e5ea-4563-a20a-f390bd3b3074@default>

On 29/09/2009 19:45, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:

> But I could certainly code the patch to just "measure
> and report" for now and we could revisit Xen's use of
> write_tsc at a later time if that's your preference.
> 
> I definitely have more patches in mind for pvrdtsc but
> may not get back to them for a few weeks, so was
> hoping to validate tsc reliability on some machines
> in the meantime.

Who's actually going to go looking for this data in their logs and report it
to you? I think we should leave this until plans are more fully formed.

 -- Keir

  reply	other threads:[~2009-09-29 19:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 20:19 [RFC] [PATCH] use "reliable" tsc properly when available, but verify Dan Magenheimer
2009-09-28 21:01 ` Keir Fraser
2009-09-28 21:06   ` Keir Fraser
2009-09-28 22:05     ` Dan Magenheimer
2009-09-29  7:43       ` Keir Fraser
2009-09-29 15:51         ` Dan Magenheimer
2009-09-29 17:17           ` Keir Fraser
2009-09-29 18:10             ` Dan Magenheimer
2009-09-29 18:21               ` Keir Fraser
2009-09-29 18:45                 ` Dan Magenheimer
2009-09-29 19:03                   ` Keir Fraser [this message]
2009-09-29 19:34                     ` Dan Magenheimer

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=C6E81883.160CD%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.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.