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/

Home

xen-devel

[Top] [All Lists]

Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code

from [Tim Deegan]

[Permanent Link][Original]

To:	Keir Fraser <keir@xxxxxxx>
Subject:	Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code
From:	Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date:	Wed, 15 Dec 2010 12:21:33 +0000
Cc:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Wed, 15 Dec 2010 04:22:21 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<C92E61F1.291BC%keir@xxxxxxx>
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:	<patchbomb.1292414371@xxxxxxxxxxxxxxxxxxxxxxx> <C92E61F1.291BC%keir@xxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Mutt/1.5.20 (2009-06-14)

At 12:15 +0000 on 15 Dec (1292415345), Keir Fraser wrote:
> Is this needed for 4.0.2 also? If so you'll need to submit a manual
> backport.

No, AFAICS it shouldn't be needed for 4.0.2; the bug was introduced when
I tinkered with the log-dirty memory allocation code recently.

Cheers,

Tim.

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, Xen Platform Team
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code, Tim Deegan [Xen-devel] [PATCH 1 of 3] x86/mm: move mfn_is_dirty along with the rest of the log-dirty code, Tim Deegan [Xen-devel] [PATCH 3 of 3] x86/mm: make paging_map_log_dirty_bitmap() static, Tim Deegan [Xen-devel] [PATCH 2 of 3] x86/mm: fix up paging_mfn_is_dirty(), Tim Deegan Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code, Keir Fraser Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code, Tim Deegan <=

Previous by Date:	Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code, Keir Fraser
Next by Date:	Re: [Xen-devel] [PATCH][TOOLS] libxl: open code basename(), Juergen Gross
Previous by Thread:	Re: [Xen-devel] [PATCH 0 of 3] Fix up locking in log-dirty code, Keir Fraser
Next by Thread:	[Xen-devel] [PATCH][TOOLS] libxl: open code basename(), Christoph Egger
Indexes:	[Date] [Thread] [Top] [All Lists]

This site is hosted by Citrix