From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] Flag events caused by foreign domains Date: Fri, 2 Dec 2011 08:11:49 +0100 Message-ID: <20111202071148.GA23017@aepfle.de> References: <2a4ec2e2ae36593aa74e.1322772973@xdev.gridcentric.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <2a4ec2e2ae36593aa74e.1322772973@xdev.gridcentric.ca> 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 Thu, Dec 01, Andres Lagar-Cavilla wrote: > Add a new flag for mem events, as consumers might need to discriminate > foreign domain-caused from guest-caused events. The vcpu field of an > event is bogus from a consumer p.o.v. for foreign domain-caused events. How is this supposed to be used? If the toolstack is going to use this then I have to say that it cant delay events much because the ring will be filled up quickly with the result that no more events can be generated until the toolstack sends responses back to the hypervisor. Olaf