xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mats Petersson <mats.petersson@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/time: fix scale_delta() inline assembly
Date: Mon, 26 Nov 2012 16:59:43 +0000	[thread overview]
Message-ID: <50B39FFF.6000209@citrix.com> (raw)
In-Reply-To: <CAF6-1L4++pq7nYVVHnOT-dV1tqPMFcJM1JVycMoKYBV6oehPJw@mail.gmail.com>

On 26/11/12 16:51, Sylvain Munaut wrote:
> I've just deployed this to a couple test servers that exhibited the problem.
>
> What I don't really understand is why are some HW affected and not others ?
I have no idea why some machines are more affected than others, but I 
can clearly see what Jan is saying, and how it will cause "weird" things 
to happen - but only if you hit the case where the calls are made in the 
right pattern, which I think is a matter of "luck". It will probably 
also matter what version of gcc is used to compile the code - different 
compiler versions will use registers in different ways.

--
Mats
>
>
> Cheers,
>
>      Sylvain
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
>

  reply	other threads:[~2012-11-26 16:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 15:23 [PATCH] x86/time: fix scale_delta() inline assembly Jan Beulich
2012-11-26 16:10 ` Keir Fraser
2012-11-26 16:43   ` Dan Magenheimer
2012-11-26 16:51     ` Sylvain Munaut
2012-11-26 16:59       ` Mats Petersson [this message]
2012-11-26 17:03       ` Jan Beulich
2012-11-26 17:12       ` Dan Magenheimer
2012-11-26 19:23         ` Keir Fraser
2012-11-26 16:53     ` Jan Beulich
2012-11-26 16:31 ` Ian Campbell
2012-11-26 16:43   ` Jan Beulich
2012-11-26 17:12     ` Ian Campbell
2012-11-26 19:22       ` Keir Fraser
2012-11-26 16:50   ` Mats Petersson

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=50B39FFF.6000209@citrix.com \
    --to=mats.petersson@citrix.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).