From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Lu8rP-0000cK-PD for qemu-devel@nongnu.org; Wed, 15 Apr 2009 13:25:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Lu8rL-0000au-2g for qemu-devel@nongnu.org; Wed, 15 Apr 2009 13:25:19 -0400 Received: from [199.232.76.173] (port=50652 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Lu8rK-0000ao-Uw for qemu-devel@nongnu.org; Wed, 15 Apr 2009 13:25:15 -0400 Received: from mx2.redhat.com ([66.187.237.31]:45801) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Lu8rK-0000Oz-Ji for qemu-devel@nongnu.org; Wed, 15 Apr 2009 13:25:14 -0400 Subject: Re: [Qemu-devel] [PATCH 2/9] struct iovec is now universally available From: Mark McLoughlin In-Reply-To: <20090415165513.GA14504@lst.de> References: <1239812969-8320-1-git-send-email-markmc@redhat.com> <1239812969-8320-2-git-send-email-markmc@redhat.com> <1239812969-8320-3-git-send-email-markmc@redhat.com> <20090415165513.GA14504@lst.de> Content-Type: text/plain Date: Wed, 15 Apr 2009 18:25:09 +0100 Message-Id: <1239816309.4431.169.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: Jan Kiszka , Anthony Liguori , qemu-devel@nongnu.org On Wed, 2009-04-15 at 18:55 +0200, Christoph Hellwig wrote: > On Wed, Apr 15, 2009 at 05:29:22PM +0100, Mark McLoughlin wrote: > > struct iovec is now defined in qemu-common.h if needed, so we don't need > > the tap code to handle !defined(HAVE_IOVEC). > > But is the writev system call also universally available? Fair point. I don't know of anywhere that qemu currently builds where writev() isn't available ... do you? >>From looking at the history, I got the impression that HAVE_IOVEC was only for windows and that doesn't use this code. Also, if it is something we want to handle, then we should do it by checking for writev() in configure and using HAVE_WRITEV Cheers, Mark.