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:35:11 +0100 Message-ID: <20111123183511.GA26144@aepfle.de> References: 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 Mon, Nov 14, Andres Lagar-Cavilla wrote: I will do a more complete review later, a few comments below. > + free_requests = RING_FREE_REQUESTS(&med->front_ring); > + if ( unlikely(free_requests < d->max_vcpus) ) > + { > + /* This may happen during normal operation (hopefully not often). */ > + gdprintk(XENLOG_INFO, "mem_event request slots for domain %d: %d\n", > + d->domain_id, free_requests); What is the purpose of this printk? The ring can and does fillup quickly with paging. > + if ( mem_event_ring_free(d, med) == 0 ) > + { > + /* This *may* happen, but only when foreign mappings generate events. */ > + gdprintk(XENLOG_WARNING, "possible lost mem_event for domain %d\n", > + d->domain_id); This printk is not needed, callers have to try again. Olaf