qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>,
	Peter Maydell <peter.maydell@linaro.org>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-s390x@nongnu.org, qemu-ppc@nongnu.org, qemu-arm@nongnu.org
Subject: [Qemu-devel] [RFC v2 0/5] generalize parsing of cpu_model (part 4)
Date: Thu, 18 Jan 2018 18:33:57 +0100	[thread overview]
Message-ID: <1516296842-136976-1-git-send-email-imammedo@redhat.com> (raw)

Based in feedback I've got on v1
   https://lists.nongnu.org/archive/html/qemu-devel/2018-01/msg04036.html

v2:
  - implemented new approach only for x86/ARM (will be done for all targets
    if approach seems acceptable)
  - add test case for '-M none -cpu FOO' case
  - redefine TARGET_DEFAULT_CPU_TYPE into CPU_RESOLVING_TYPE
  - scrape off default cpu_model refactoring, so it would cause
    less conflicts with Laurent's series where he tries to rework
    defaults to use ELF hints of executed program

End goal of series is still the same as v1, i.e. get rid of cpu_init() API
and limit cpu_model handling only to places where it must be done.

CC: Laurent Vivier <laurent@vivier.eu>
CC: Peter Maydell <peter.maydell@linaro.org>
CC: Eduardo Habkost <ehabkost@redhat.com>
CC: qemu-s390x@nongnu.org
CC: qemu-ppc@nongnu.org
CC: qemu-arm@nongnu.org

Igor Mammedov (5):
  tests: add machine 'none' with -cpu test
  machine: prepare machine 'none' to gradually switch to cpu_create()
    API
  linux-user: prepare for switching to cpu_create() API
  arm: cpu: add CPU_RESOLVING_TYPE macro
  x86: cpu: add CPU_RESOLVING_TYPE macro

 target/arm/cpu.h       |  3 ++
 target/i386/cpu.h      |  3 ++
 hw/core/null-machine.c | 13 ++++++++-
 linux-user/main.c      | 15 ++++++++--
 tests/Makefile.include |  2 ++
 tests/machine-none.c   | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++
 vl.c                   |  8 +++++-
 7 files changed, 114 insertions(+), 5 deletions(-)
 create mode 100644 tests/machine-none.c

-- 
2.7.4

             reply	other threads:[~2018-01-18 17:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 17:33 Igor Mammedov [this message]
2018-01-18 17:33 ` [Qemu-devel] [RFC v2 1/5] tests: add machine 'none' with -cpu test Igor Mammedov
2018-01-18 19:01   ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-01-18 17:33 ` [Qemu-devel] [RFC v2 2/5] machine: prepare machine 'none' to gradually switch to cpu_create() API Igor Mammedov
2018-01-18 19:06   ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-01-18 20:35     ` Eduardo Habkost
2018-01-18 17:34 ` [Qemu-devel] [RFC v2 3/5] linux-user: prepare for switching " Igor Mammedov
2018-01-18 19:10   ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2018-01-18 20:33   ` [Qemu-devel] " Eduardo Habkost
2018-01-19 10:24     ` Igor Mammedov
2018-01-18 17:34 ` [Qemu-devel] [RFC v2 4/5] arm: cpu: add CPU_RESOLVING_TYPE macro Igor Mammedov
2018-01-18 17:34 ` [Qemu-devel] [RFC v2 5/5] x86: " Igor Mammedov
2018-01-18 17:59 ` [Qemu-devel] [RFC v2 0/5] generalize parsing of cpu_model (part 4) no-reply
2018-01-18 20:17 ` no-reply

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=1516296842-136976-1-git-send-email-imammedo@redhat.com \
    --to=imammedo@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=qemu-s390x@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).