|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available
On 29/09/2009 19:45, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> 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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Keir Fraser
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Keir Fraser
- RE: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Keir Fraser
- RE: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Keir Fraser
- RE: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Keir Fraser
- RE: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
- Re: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify,
Keir Fraser <=
- RE: [Xen-devel] [RFC] [PATCH] use "reliable" tsc properly when available, but verify, Dan Magenheimer
|
|
|
|
|