WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH] x86: unconditionally mark TSC unstable under

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] x86: unconditionally mark TSC unstable under Xen
From: Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx>
Date: Mon, 16 Aug 2010 01:27:46 +0000
Cc: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jed Smith <jed@xxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Sun, 15 Aug 2010 18:28:36 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JqS9LdusWSXwn5OfIrU7IeoO375+a6pExiW4L6K/X2Q=; b=MhuPO2mI6z6Ge55TCcVDLnfREqiZftWtuIcP99Lh1y+83ELGaaM4IpoFuchCYOYE6D IM4l/glAbtJI3cCbaQZJNBcMl27YRYyFAiDM6Xce8hF8dQp0Arg+kybK79o/jfrMRxWV U6nKPGovjdczCAqyXQx8Q3ZCdKQPpr+t5zHRk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=BuyliEEZ1EM6sNaTzNcSKK4kzZAqctKz0GDGHepKiqkb0bSC6n7PoUR5EZgOdxPNfD qM+INtW7nFJNVyzpdNdKabHfCRZ5k+xBy9qBB8bX6fSXQwAB4cgXEGkOuNZgXxyHCU9u Usr8nhUcmFDVqdaN4AsFlnx6UkZ2VinMDVliQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C687ADE.3020100@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <51C8308F-F413-47AF-8845-C92BD36CA35C@xxxxxxxxxx> <4C3E2DCC.1010201@xxxxxxxx> <b97b2105-e814-471e-b87f-0e2bc5bcbec6@default> <4C3F3B0F.1040107@xxxxxxxx> <cada2c9b-1e49-40ad-976e-2ee781d77a7c@default> <4C3F4DFF.3070607@xxxxxxxx> <AANLkTinc=w4mRGoCEumsNCfbUVOJbycaH4Omem5eB6th@xxxxxxxxxxxxxx> <4C687ADE.3020100@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sun, Aug 15, 2010 at 23:40, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
>  On 08/15/2010 01:57 PM, Ævar Arnfjörð Bjarmason wrote:
>> Hi all, I was wondering what the status on this issue was. Maybe I've
>> missed something, but I've looked through the lkml and xen archives and
>> I haven't found a re-rolled patch that addresses this issue.
>>
>> I'm not very familiar with this area (well, any area) of the kernel,
>> but if there's something needed to push this forward I'd be happy to
>> help with that, or if this is already being addressed somewhere else a
>> pointer to where that is would be welcome.
>
> A patch that fixes this is in mainline and all the supported stable
> kernels.  Itis "xen: drop xen_sched_clock in favour of using plain
> wallclock time".

Thanks! I didn't spot that when looking through your patches.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>