From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NfzKB-0001gF-Vb for qemu-devel@nongnu.org; Fri, 12 Feb 2010 12:29:04 -0500 Received: from [199.232.76.173] (port=51200 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NfzKB-0001fo-Fl for qemu-devel@nongnu.org; Fri, 12 Feb 2010 12:29:03 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NfzKA-00066u-AC for qemu-devel@nongnu.org; Fri, 12 Feb 2010 12:29:03 -0500 Received: from mail-vw0-f45.google.com ([209.85.212.45]:56294) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NfzKA-00066q-1B for qemu-devel@nongnu.org; Fri, 12 Feb 2010 12:29:02 -0500 Received: by vws11 with SMTP id 11so579427vws.4 for ; Fri, 12 Feb 2010 09:29:01 -0800 (PST) Message-ID: <4B758FD9.2010807@codemonkey.ws> Date: Fri, 12 Feb 2010 11:28:57 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Heads up: glibc preadv emulation breaks qemu on older kernels References: <20100211190608.GA26410@amd.home.annexia.org> <20100212125238.GA22221@lst.de> <20100212135044.GA24209@lst.de> In-Reply-To: <20100212135044.GA24209@lst.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Hellwig Cc: qemu-devel@nongnu.org, "Richard W.M. Jones" On 02/12/2010 07:50 AM, Christoph Hellwig wrote: > On Fri, Feb 12, 2010 at 04:49:23PM +0300, malc wrote: > >> On Fri, 12 Feb 2010, Christoph Hellwig wrote: >> >> >>> On Thu, Feb 11, 2010 at 07:06:08PM +0000, Richard W.M. Jones wrote: >>> >>>> One interesting thing is that qemu has its own preadv emulation (which >>>> does the emulation correctly), but this is never used because qemu >>>> never gets ENOSYS back from preadv. >>>> >>> At this point the amount of bugs in the glibc preadv/pwritev code really >>> make me want to go to use the raw system calls on Linux only. Any >>> opinions from the maintainers if that is acceptable? >>> >> There are more than one way to parse the first sentence, if it should be >> read as: >> On linux and on linux only avoid using pread/write[v] and talk to the >> kernel directly. >> >> Then i agree. >> > Yes. The BSDs tend to not play stupid emulation games in the libc, so > changes of these kinds of messups to happen are far less. > In all fairness, I seem to recall there being a problem with the kernel implementation of preadv/pwritev too. I think a configure option would be in order. Forever avoiding glibc is probably a bit extreme. Regards, Anthony Liguori > >