[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTik_hRn9acIuuRBJDWLuQVUh9qE-blvgFmUQvzlz@mail.gmail.com>
Date: Tue, 13 Jul 2010 11:15:09 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Avi Kivity <avi@...hat.com>
Cc: Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
Peter Palfrader <peter@...frader.org>,
Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
stable@...nel.org, stable-review@...nel.org,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
Glauber Costa <glommer@...hat.com>,
Zachary Amsden <zamsden@...hat.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: [patch 134/149] x86, paravirt: Add a global synchronization point
for pvclock
On Tue, Jul 13, 2010 at 11:04 AM, Avi Kivity <avi@...hat.com> wrote:
>
> Well, current upstream uses "m":
Yes, I'd expect current 2.6.34 to also show the same problem.
> and works; I also failed to reproduce with 2.6.32.16. So I expect some
> toolchain involvement.
And yes, I do believe it's likely a newer gcc that triggers it too,
otherwise we'd have seen more reports of it.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists