From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NhKsK-0002Ra-3n for qemu-devel@nongnu.org; Tue, 16 Feb 2010 05:41:52 -0500 Received: from [199.232.76.173] (port=59195 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NhKsJ-0002RE-05 for qemu-devel@nongnu.org; Tue, 16 Feb 2010 05:41:51 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NhKsI-0004sK-CB for qemu-devel@nongnu.org; Tue, 16 Feb 2010 05:41:50 -0500 Received: from mx1.redhat.com ([209.132.183.28]:29645) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NhKsH-0004sG-UH for qemu-devel@nongnu.org; Tue, 16 Feb 2010 05:41:50 -0500 Message-ID: <4B7A7667.6010601@redhat.com> Date: Tue, 16 Feb 2010 12:41:43 +0200 From: Avi Kivity 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> <4B758FD9.2010807@codemonkey.ws> <20100215221638.GA19495@lst.de> In-Reply-To: <20100215221638.GA19495@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: "Richard W.M. Jones" , qemu-devel@nongnu.org On 02/16/2010 12:16 AM, Christoph Hellwig wrote: > On Fri, Feb 12, 2010 at 11:28:57AM -0600, Anthony Liguori wrote: > >>> 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 would be surprised by that as it's just an entirely trivial entry > point to long existant infrastructure. I even checked the commit logs > and that code hasn't been touched at all since the initial commit. > So if people have problems with it, please report it.. > IIRC there was a problem with wiring up glibc to use p*v on i386. The large number and size of the arguments caused some confusion wrt the calling convention, or something. So it's only fair that glibc emulation of the syscall would be broken too. -- error compiling committee.c: too many arguments to function