qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>, qemu-ppc@nongnu.org
Cc: Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, abologna@redhat.com,
	bharata@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 1/5] ppc: Introduce a function to look up CPU alias strings
Date: Tue,  9 Aug 2016 11:17:05 +0200	[thread overview]
Message-ID: <1470734229-10832-2-git-send-email-thuth@redhat.com> (raw)
In-Reply-To: <1470734229-10832-1-git-send-email-thuth@redhat.com>

We will need this function to look up the aliases in the
spapr-cpu-core code, too.

Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 target-ppc/cpu.h            |  1 +
 target-ppc/translate_init.c | 13 +++++++++++++
 2 files changed, 14 insertions(+)

diff --git a/target-ppc/cpu.h b/target-ppc/cpu.h
index 5fce1ff..786ab5c 100644
--- a/target-ppc/cpu.h
+++ b/target-ppc/cpu.h
@@ -1201,6 +1201,7 @@ extern const struct VMStateDescription vmstate_ppc_cpu;
 /*****************************************************************************/
 PowerPCCPU *cpu_ppc_init(const char *cpu_model);
 void ppc_translate_init(void);
+const char *ppc_cpu_lookup_alias(const char *alias);
 void gen_update_current_nip(void *opaque);
 /* you can call this signal handler from your SIGBUS and SIGSEGV
    signal handlers to inform the virtual CPU of exceptions. non zero
diff --git a/target-ppc/translate_init.c b/target-ppc/translate_init.c
index 5f28a36..7a9b15e 100644
--- a/target-ppc/translate_init.c
+++ b/target-ppc/translate_init.c
@@ -10012,6 +10012,19 @@ static ObjectClass *ppc_cpu_class_by_name(const char *name)
     return NULL;
 }
 
+const char *ppc_cpu_lookup_alias(const char *alias)
+{
+    int ai;
+
+    for (ai = 0; ppc_cpu_aliases[ai].alias != NULL; ai++) {
+        if (strcmp(ppc_cpu_aliases[ai].alias, alias) == 0) {
+            return ppc_cpu_aliases[ai].model;
+        }
+    }
+
+    return NULL;
+}
+
 PowerPCCPU *cpu_ppc_init(const char *cpu_model)
 {
     return POWERPC_CPU(cpu_generic_init(TYPE_POWERPC_CPU, cpu_model));
-- 
1.8.3.1

  reply	other threads:[~2016-08-09  9:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  9:17 [Qemu-devel] [PATCH for-2.7 0/5] spapr: Fix regression in CPU alias handling Thomas Huth
2016-08-09  9:17 ` Thomas Huth [this message]
2016-08-09  9:17 ` [Qemu-devel] [PATCH 2/5] hw/ppc/spapr: Look up CPU alias names instead of hard-coding the aliases Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 3/5] hw/ppc/spapr: Do not leak the memory of the type string Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 4/5] ppc/kvm: Do not mess up the generic CPU family registration Thomas Huth
2016-08-09  9:17 ` [Qemu-devel] [PATCH 5/5] ppc/kvm: Register also a generic spapr CPU core family type Thomas Huth
2016-08-09 11:27 ` [Qemu-devel] [PATCH for-2.7 0/5] spapr: Fix regression in CPU alias handling Andrea Bolognani
2016-08-09 15:39 ` Bharata B Rao
2016-08-09 16:22   ` Thomas Huth
2016-08-09 16:37     ` Andrea Bolognani
2016-08-09 15:56 ` Thomas Huth

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=1470734229-10832-2-git-send-email-thuth@redhat.com \
    --to=thuth@redhat.com \
    --cc=abologna@redhat.com \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).