From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com, kurt.hackel@oracle.com, "Dugger,
Donald D" <donald.d.dugger@intel.com>,
"Xu, Dongxiao" <dongxiao.xu@intel.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: Live migration fails due to c/s 20627
Date: Tue, 15 Dec 2009 22:19:11 -0800 [thread overview]
Message-ID: <4B287BDF.8020308@goop.org> (raw)
In-Reply-To: <562bba8c-64a3-4876-b0ff-ae9349c76d3c@default>
On 12/15/2009 08:14 PM, Dan Magenheimer wrote:
> My argument is simply that if TSC_AUX cannot ALWAYS
> be trusted by an application, apps will NEVER trust it.
> And if apps NEVER trust it, why expose it at all?
>
The cpu/node info is only of heuristic value anyway; it is never
trustworthy in an absolute sense. Apps just use it to try to optimise
their own memory allocation and use patterns, but they can't rely on
that info for actual correctness.
J
next prev parent reply other threads:[~2009-12-16 6:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 18:02 Live migration fails due to c/s 20627 Dan Magenheimer
2009-12-14 23:19 ` Keir Fraser
2009-12-15 4:40 ` Xu, Dongxiao
2009-12-15 15:56 ` Dan Magenheimer
2009-12-15 16:10 ` Xu, Dongxiao
2009-12-15 16:31 ` Dan Magenheimer
2009-12-15 17:08 ` Dan Magenheimer
2009-12-15 18:04 ` Xu, Dongxiao
2009-12-16 2:07 ` Nakajima, Jun
2009-12-16 2:43 ` Zhang, Xiantao
2009-12-16 4:14 ` Dan Magenheimer
2009-12-16 5:07 ` Zhang, Xiantao
2009-12-16 16:23 ` Dan Magenheimer
2009-12-16 17:38 ` Jeremy Fitzhardinge
2009-12-16 6:19 ` Jeremy Fitzhardinge [this message]
2009-12-16 15:20 ` Dan Magenheimer
2009-12-16 17:31 ` Jeremy Fitzhardinge
2009-12-15 17:12 ` Jeremy Fitzhardinge
2009-12-15 17:24 ` Xu, Dongxiao
2009-12-15 18:25 ` Jeremy Fitzhardinge
2009-12-15 19:20 ` Dan Magenheimer
2009-12-15 19:31 ` Keir Fraser
2009-12-15 19:52 ` Keir Fraser
2009-12-16 15:41 ` Andre Przywara
2009-12-16 16:54 ` Dan Magenheimer
2009-12-15 19:25 ` Keir Fraser
2009-12-15 18:05 ` Xu, Dongxiao
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=4B287BDF.8020308@goop.org \
--to=jeremy@goop.org \
--cc=dan.magenheimer@oracle.com \
--cc=donald.d.dugger@intel.com \
--cc=dongxiao.xu@intel.com \
--cc=jun.nakajima@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=kurt.hackel@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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.