From: Keir Fraser <keir.xen@gmail.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>,
Sylvain Munaut <s.munaut@whatever-company.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86/time: fix scale_delta() inline assembly
Date: Mon, 26 Nov 2012 19:23:28 +0000 [thread overview]
Message-ID: <CCD97230.460F4%keir.xen@gmail.com> (raw)
In-Reply-To: <fd048b2a-ec5d-4c0e-a800-7567eecc4211@default>
On 26/11/2012 17:12, "Dan Magenheimer" <dan.magenheimer@oracle.com> wrote:
>> From: Sylvain Munaut [mailto:s.munaut@whatever-company.com]
>> Subject: Re: [Xen-devel] [PATCH] x86/time: fix scale_delta() inline assembly
>>
>> 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 don't know, but I'd imagine there is something in the x86 platform
> software (aka firmware) of those machines that runs and blocks execution
> of Xen for long enough (via NMI/MCE/SMI) for the platform timer to
> overflow, and this doesn't occur on other machines.
It is just luck of the draw. There is no actual platform timer overflow
happening when this bug triggers.
-- Keir
> Maybe Jan has a better idea...
next prev parent reply other threads:[~2012-11-26 19:23 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
2012-11-26 17:03 ` Jan Beulich
2012-11-26 17:12 ` Dan Magenheimer
2012-11-26 19:23 ` Keir Fraser [this message]
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=CCD97230.460F4%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=dan.magenheimer@oracle.com \
--cc=s.munaut@whatever-company.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 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.