qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Rigby <john.rigby@linaro.org>
To: qemu-devel@nongnu.org
Cc: 'Peter Maydell <peter.maydell@linaro.org>,
	John Rigby <john.rigby@linaro.org>,
	Riku Voipio <riku.voipio@iki.fi>, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] [PATCH v3 resend 05/11] linux-user: Don't treat aarch64 cpu names specially
Date: Mon, 13 May 2013 00:57:52 -0600	[thread overview]
Message-ID: <1368428278-29299-6-git-send-email-john.rigby@linaro.org> (raw)
In-Reply-To: <1368428278-29299-1-git-send-email-john.rigby@linaro.org>

From: Alexander Graf <agraf@suse.de>

32-bit ARM has a lot of different names for different types of CPUs it supports.
On AArch64, we don't have this, so we really don't want to execute the 32-bit
logic. Stub it out for AArch64 linux-user guests.

Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: John Rigby <john.rigby@linaro.org>
---
 linux-user/cpu-uname.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/linux-user/cpu-uname.c b/linux-user/cpu-uname.c
index 59cd647..89bdb91 100644
--- a/linux-user/cpu-uname.c
+++ b/linux-user/cpu-uname.c
@@ -30,7 +30,8 @@
  * return here */
 const char *cpu_to_uname_machine(void *cpu_env)
 {
-#ifdef TARGET_ARM
+#if defined(TARGET_ARM) && !defined(TARGET_AARCH64)
+
     /* utsname machine name on linux arm is CPU arch name + endianness, e.g.
      * armv7l; to get a list of CPU arch names from the linux source, use:
      *     grep arch_name: -A1 linux/arch/arm/mm/proc-*.S
-- 
1.8.2.2

  parent reply	other threads:[~2013-05-13  6:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13  6:57 [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 01/11] ARM: Export cpu_env John Rigby
2013-05-13  9:28   ` Peter Maydell
2013-05-13 10:07     ` Alexander Graf
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 02/11] ARM: Prepare translation for AArch64 code John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 03/11] ARM: Add AArch64 translation stub John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 04/11] AArch64: Add gdb stub John Rigby
2013-05-13  6:57 ` John Rigby [this message]
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 06/11] linux-user: Add syscall handling for AArch64 John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 07/11] linux-user: Fix up AArch64 syscall handlers John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 08/11] linux-user: Add signal handling for AArch64 John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 09/11] linux-user: Add AArch64 support John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 10/11] ARM: Add aarch64 target to configure John Rigby
2013-05-13  6:57 ` [Qemu-devel] [PATCH v3 resend 11/11] linux-user: AArch64 requires at least 3.8.0 John Rigby
2013-05-13  8:54 ` [Qemu-devel] [PATCH v3 resend 00/11] AArch64 preparation patch set Peter Maydell
2013-05-13 13:40   ` John Rigby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1368428278-29299-6-git-send-email-john.rigby@linaro.org \
    --to=john.rigby@linaro.org \
    --cc=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).