From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49600) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKQcb-0001LD-AO for qemu-devel@nongnu.org; Wed, 29 Jul 2015 08:38:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZKQcY-000262-PW for qemu-devel@nongnu.org; Wed, 29 Jul 2015 08:38:09 -0400 Received: from mail-ob0-x22e.google.com ([2607:f8b0:4003:c01::22e]:34905) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZKQcY-00025w-Jx for qemu-devel@nongnu.org; Wed, 29 Jul 2015 08:38:06 -0400 Received: by obbop1 with SMTP id op1so5947212obb.2 for ; Wed, 29 Jul 2015 05:38:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <55B734A7.8040108@gmx.net> <55B8B122.7020406@gmx.net> Date: Wed, 29 Jul 2015 14:38:06 +0200 Message-ID: From: Karel Gardas Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] Debian 7.8.0 SPARC64 on qemu - anything i can do to speedup the emulation? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dennis Luehring Cc: qemu-devel@nongnu.org aarch64 booted, this is ubuntu 14.04.1 LTS, LSB: ubuntu@ubuntu:~$ file /bin//bash /bin//bash: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.7.0, BuildID[sha1]=36b671892d00161eaeb9f602049f9ce830e9056e, stripped ubuntu@ubuntu:~$ cat /proc/cpuinfo Processor : AArch64 Processor rev 0 (aarch64) processor : 0 Features : fp asimd evtstrm CPU implementer : 0x41 CPU architecture: AArch64 CPU variant : 0x1 CPU part : 0xd07 CPU revision : 0 Hardware : linux,dummy-virt On Wed, Jul 29, 2015 at 2:34 PM, Karel Gardas wrote: > On Wed, Jul 29, 2015 at 12:55 PM, Dennis Luehring wrote: >> Am 29.07.2015 um 11:17 schrieb Karel Gardas: >>> >>> What was interesting was that nbench2 was comparable on aarch64 >> >> >> was aarch64 a little or big-endian system, with unaligned accesses possible? > > This was Ubuntu with Linux kernel 3.13 so I guess little and unaligned > possible to make least pain for developers. -- but I'm just guessing > since I can't boot that now, it was always a little bit tricky to boot > that btw. Once it boots, tell me how to find the asnwers to your > questions. Will dmesg do or cat /proc/cpuinfo or just file /bin/bash?