From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Andres Lagar-Cavilla" Subject: Re: [PATCH] Testing for mem event ring management Date: Mon, 20 Feb 2012 11:57:51 -0800 Message-ID: References: <330baa2bb903e24d67b7.1326386501@xdev.gridcentric.ca> <20290.28974.328634.111629@mariner.uk.xensource.com> Reply-To: andres@lagarcavilla.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20290.28974.328634.111629@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: olaf@aepfle.de, xen-devel@lists.xensource.com, tim@xen.org, andres@gridcentric.ca, adin@gridcentric.ca List-Id: xen-devel@lists.xenproject.org > Andres Lagar-Cavilla writes ("[Xen-devel] [PATCH] Testing for mem event > ring management"): >> This is example code, not meant for tree consumption. So >> that others can run tests on the ring management bits. > > Is this supposed to apply to tip, and build ? It was, way back when. This isn't a significant diff from tests/xen-access either -- Effecitvely, it just sets a different mem_access type (n2rwx, instead of rw2rx) Andres > > memoper.c:48: error: expected specifier-qualifier-list before > 'mem_event_t' > memoper.c: In function 'wait_for_event_or_timeout': > memoper.c:66: error: 'memaccess_t' has no member named 'mem_event' > memoper.c:99: error: 'memaccess_t' has no member named 'mem_event' > ... > > Ian. >