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 Products Support Community News


Re: [PATCH] Re: tmem on 4.1 (was [Xen-devel] Re: Freeze schedule)

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [PATCH] Re: tmem on 4.1 (was [Xen-devel] Re: Freeze schedule)
From: Keir Fraser <keir@xxxxxxx>
Date: Thu, 20 Jan 2011 07:17:41 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Wed, 19 Jan 2011 23:18:37 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:user-agent:date:subject:from:to:cc :message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=ros/2AA4IenrCIJen6GbN6gYOgxUgps+fGwFMB3khes=; b=uFaPWdQmy+btgcbnV0W3LYi6MVN8YDcCihY7fm0GEzuOjxirB+71It1s1fQ9KH74TV DST8fNbi/zHG+fJdeYf+VFXuNeYOmVh1WxTg5SyWPBMzYCsg6kM6QCDnZfcgqzC3qZ8/ ADr4iMD7uzFSenRfxX05VLR6IzMOs5/0HkuF0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=WVlebLY/azNs9c2Ix72JuDa9JMuJvr86TSPpBvHi/1aJjezOA3x9sI4PRdU0CLKMav xf6mgpeZwWTvduiTLjVy2llceDd4dev93xJe0C99pRGjumJc0mp8Q13DWH+HgXA+88Jp kAa6D8e1E/YyOgH/xcGqal2R5ZzbPsbkTzghU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <8a563a46-bdbb-407f-9455-2eaedc773dfc@default>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acu4ch/U/E7SIKUXIk2Ku1XmM9Dmcg==
Thread-topic: [PATCH] Re: tmem on 4.1 (was [Xen-devel] Re: Freeze schedule)
User-agent: Microsoft-Entourage/
On 19/01/2011 21:38, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> Just to check again, has anyone actually seen a problem with
> tmem enabled by default recently?  I agree that there is still
> theoretically a problem, but there is the same problem with
> normal guests doing lots of ballooning as well.  Also, note
> that even if tmem defaults to enabled, the problem is impossible
> unless a guest enables tmem (or, in the case of SuSE, dom0).
> And even if a guest does enable tmem, the problem manifested
> largely due to shadow pages using order>0 (now fixed?)...
> failure on domain creation can happen for many reasons and
> is much less of an issue, true?
> Feel free to shoot me down with more evidence, but I have
> to at least provide token resistance to this patch.  Distros
> might certainly choose to disable it to avoid any risk at
> all, but turning it off anymore seems overkill for xen.org
> open source Xen IMHO.

Tbh I was wondering whether anyone is really using it in earnest. No
upstream kernels support it? If noone's using it, who really cares whether
it's enabled or not, apart from its author.

 -- Keir

> Dan

Xen-devel mailing list