From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Jones Subject: Re: Re: xen_sched_clock problem in RHEL6b2, Was: [PATCH] x86: unconditionally mark TSC unstable under Xen Date: Mon, 19 Jul 2010 09:00:17 +0200 Message-ID: <4C43F801.40204@redhat.com> References: <002b7702-f446-427f-8048-27d4edd7a51e@default> <4C43E9EC.9030007@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C43E9EC.9030007@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michal Novotny Cc: Dan Magenheimer , xen-devel@lists.xensource.com, Jeremy Fitzhardinge , Jan Beulich , Jed Smith List-Id: xen-devel@lists.xenproject.org On 07/19/2010 08:00 AM, Michal Novotny wrote: > Andrew, could you please have a look this one? I don't know whether it's > RHEL-6 kernel bug itself or whether there's some bug in the hypervisor, > nevetheless both parts belongs to the same component - kernel-xen - > you're working on so I guess you're a good guy to ask. Please, leave me > in the CC list as I'm interested as well. Yup, I've been watching this thread. I haven't seen anything strange with my rhel6 testing yet, but Jeremy's explanation makes sense, so I'm considering the patch. Andrew