From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NdZbq-0000I4-R0 for qemu-devel@nongnu.org; Fri, 05 Feb 2010 20:37:18 -0500 Received: from [199.232.76.173] (port=40292 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NdZbq-0000Hr-Bm for qemu-devel@nongnu.org; Fri, 05 Feb 2010 20:37:18 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NdZbp-0002x7-9A for qemu-devel@nongnu.org; Fri, 05 Feb 2010 20:37:17 -0500 Received: from mail-pz0-f187.google.com ([209.85.222.187]:59745) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NdZbo-0002wX-Ig for qemu-devel@nongnu.org; Fri, 05 Feb 2010 20:37:16 -0500 Received: by pzk17 with SMTP id 17so316718pzk.4 for ; Fri, 05 Feb 2010 17:37:15 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B6CA26C.3060106@mail.berlios.de> References: <761ea48b0907110814t12c644b6mf733d3b5e28e152@mail.gmail.com> <20091017195726.GB9922@laped.iglesias.mooo.com> <20091018030944.GB15656@shareable.org> <761ea48b0910180429l9fdf32r7f0a8f7ceebb9eee@mail.gmail.com> <4B6CA26C.3060106@mail.berlios.de> Date: Sat, 6 Feb 2010 02:37:14 +0100 Message-ID: <761ea48b1002051737k6d6d33a5pbdcdf0e2527988c1@mail.gmail.com> Subject: Re: [Qemu-devel] [PATCH] User mode: Handle x86_64 vsyscall From: Laurent Desnogues Content-Type: text/plain; charset=ISO-8859-1 List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: "Edgar E. Iglesias" , qemu-devel@nongnu.org On Fri, Feb 5, 2010 at 11:57 PM, Stefan Weil wrote: > Laurent Desnogues schrieb: [...] > > I'm still struggling with bntest and other x86_64-linux-user software > calling any of the vsyscall functions. > > Laurent, your vsyscall patch only works on x86_64 hosts. > > A lot of software calls time() which uses vsyscall on x86_64 which > does not work with x86_64-linux-user mode. I'm not sure I understand what you mean. Did you try on some other host and it failed? Was your host 32-bit? If so, I'm afraid user-mode will fail for more reasons than vsyscall. > So the status of x86_64-linux-user is not more than experimental :-( > > I tried to modify x86_64-linux-user to set up a vsyscall page in high > memory, > but this seems to be difficult (at least with 32 bit host). > > Any hints how this should be done are welcome. My patch explicitly prevents the linking of the vsyscall page. Could you provide more info about your host? Laurent