From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: Balloon device in qemu?
Date: Mon, 18 Aug 2008 09:03:53 -0500
Message-ID: <48A98149.9060502@us.ibm.com>
References: <4891B7C2.70800@qumranet.com> <20080801190654.GA24342@dmt.cnet> <4893685B.1080409@us.ibm.com> <20080802130123.GK27246@duo.random> <489655E8.4070401@us.ibm.com> <4896BEBA.4020209@redhat.com> <20080804115649.GF11476@duo.random> <48A98069.7020104@qumranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Andrea Arcangeli <andrea@qumranet.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KVM list <kvm@vger.kernel.org>
To: Avi Kivity <avi@qumranet.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from e1.ny.us.ibm.com ([32.97.182.141]:60912 "EHLO e1.ny.us.ibm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752762AbYHROEe (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 18 Aug 2008 10:04:34 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234])
	by e1.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id m7IE4YJx010061
	for <kvm@vger.kernel.org>; Mon, 18 Aug 2008 10:04:34 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m7IE4X14191924
	for <kvm@vger.kernel.org>; Mon, 18 Aug 2008 10:04:33 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1])
	by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m7IE4Xx8031787
	for <kvm@vger.kernel.org>; Mon, 18 Aug 2008 10:04:33 -0400
In-Reply-To: <48A98069.7020104@qumranet.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Avi Kivity wrote:
> Andrea Arcangeli wrote:
>> I'm more worried about the fact that with Anthony's plan ballooning
>> will be unusable for a long while on enterprise distros, as it will
>> take a while before they run on a >=2.6.27 kernel. So I wonder if a
>> compact layer is worth it. But surely initially we can modify
>> KVM_CAP_SYNC_MMU to not be set if kernel isn't compiled with
>> CONFIG_MMU_NOTIFIER=y and we can add the compact layer later if needed.
>>   
>
> I added something to hack-module.awk, so KVM_CAP_SYNC_MMU is now 
> reliable.

Great, I'll update the balloon backend and resubmit this afternoon.

Regards,

Anthony Liguori