From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH 1 of 4] Improve ring management for memory events Date: Wed, 23 Nov 2011 19:57:28 +0100 Message-ID: <20111123185728.GA27583@aepfle.de> References: <20111123183511.GA26144@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andres Lagar-Cavilla Cc: andres@gridcentric.ca, xen-devel@lists.xensource.com, tim@xen.org, keir.xen@gmail.com, adin@gridcentric.ca List-Id: xen-devel@lists.xenproject.org On Wed, Nov 23, Andres Lagar-Cavilla wrote: > Well, we can tone down printk's to be debug level. I don't think they're > unnecessary if they're made an optional debug tool. There is nothing to debug here, since the callers have to retry anyway. > Question: I have one vcpu, how do I fill up the ring quickly? (outside of > foreign mappings) Have a balloon driver in the guest and balloon down more than 64*PAGE_SIZE. This is the default at least in my setup where the kernel driver releases some memory right away (I havent checked where this is actually configured). Olaf