From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGY91-0005HZ-Pz for qemu-devel@nongnu.org; Thu, 20 Feb 2014 13:14:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WGY8y-0000VI-Ss for qemu-devel@nongnu.org; Thu, 20 Feb 2014 13:14:47 -0500 Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::3]:38999) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WGY8y-0000Tt-I9 for qemu-devel@nongnu.org; Thu, 20 Feb 2014 13:14:44 -0500 Date: Thu, 20 Feb 2014 19:14:36 +0100 From: Olaf Hering Message-ID: <20140220181436.GA19843@aepfle.de> References: <1391702379-20042-1-git-send-email-olaf@aepfle.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v2] xen_disk: add discard support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefano Stabellini Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com On Thu, Feb 20, Stefano Stabellini wrote: > On Thu, 6 Feb 2014, Olaf Hering wrote: > > @@ -253,6 +254,8 @@ static int ioreq_parse(struct ioreq *ioreq) > > case BLKIF_OP_WRITE: > > ioreq->prot = PROT_READ; /* from memory */ > > break; > > + case BLKIF_OP_DISCARD: > > + return 0; > > default: > > xen_be_printf(&blkdev->xendev, 0, "error: unknown operation (%d)\n", > > ioreq->req.operation); > > Unfortunately I didn't realize before that older Xen releases don't > define BLKIF_OP_DISCARD, therefore this patch would cause QEMU build > failures against Xen 4.1 for example. Why would that matter? Is new qemu seriously supposed to work with stale Xen releases? But I will have a look how to solve this. Olaf