From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KQ408-0000yQ-2j for qemu-devel@nongnu.org; Mon, 04 Aug 2008 13:37:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KQ406-0000xl-Dc for qemu-devel@nongnu.org; Mon, 04 Aug 2008 13:37:43 -0400 Received: from [199.232.76.173] (port=35374 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KQ406-0000xe-3y for qemu-devel@nongnu.org; Mon, 04 Aug 2008 13:37:42 -0400 Received: from smtp.eu.citrix.com ([62.200.22.115]:46765) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KQ406-0007iE-4W for qemu-devel@nongnu.org; Mon, 04 Aug 2008 13:37:42 -0400 Date: Mon, 4 Aug 2008 18:37:37 +0100 From: Samuel Thibault Subject: Re: [Qemu-devel] [PATCH 5/7] xen: add block device backend driver. Message-ID: <20080804173737.GA4470@implementation.uk.xensource.com> References: <1217865045-10722-1-git-send-email-kraxel@redhat.com> <1217865045-10722-6-git-send-email-kraxel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: xen-devel@lists.xensource.com, Gerd Hoffmann Blue Swirl, le Mon 04 Aug 2008 20:26:42 +0300, a écrit : > > + RING_PUSH_RESPONSES_AND_CHECK_NOTIFY(&blkdev->rings.common, send_notify); > > EUGLY_LONG_NAME_WITH_ALL_CAPS That's unfortunately the xen API. > Why different protocols for i386 and x86_64? Because the xen block shared structures have been defined at API level, not ABI, so they differ. > Would I need to add Sparc32 and Sparc64 versions some day? Should there be a Xen port to these archs, yes. Samuel