From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
qemu-s390x@nongnu.org, qemu-arm@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [RFC v2 3/5] linux-user: prepare for switching to cpu_create() API
Date: Fri, 19 Jan 2018 11:24:23 +0100 [thread overview]
Message-ID: <20180119112423.683a73ef@redhat.com> (raw)
In-Reply-To: <20180118203337.GE5292@localhost.localdomain>
On Thu, 18 Jan 2018 18:33:37 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Thu, Jan 18, 2018 at 06:34:00PM +0100, Igor Mammedov wrote:
> > temporarily add #ifdef CPU_RESOLVING_TYPE in linux-user/main.c
> > so that each target could gradually switch to cpu_create() and
> > not converted yet could continue to use cpu_init().
> >
> > Once all targets are converted
> > temporary ifdefs and cpu_init() API
> > will be removed
> >
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > linux-user/main.c | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/linux-user/main.c b/linux-user/main.c
> > index 450eb3c..d481e8c 100644
> > --- a/linux-user/main.c
> > +++ b/linux-user/main.c
> > @@ -44,6 +44,7 @@ static const char *argv0;
> > static int gdbstub_port;
> > static envlist_t *envlist;
> > static const char *cpu_model;
> > +static const char *cpu_type;
> > unsigned long mmap_min_addr;
> > unsigned long guest_base;
> > int have_guest_base;
> > @@ -3847,7 +3848,7 @@ void init_task_state(TaskState *ts)
> > CPUArchState *cpu_copy(CPUArchState *env)
> > {
> > CPUState *cpu = ENV_GET_CPU(env);
> > - CPUState *new_cpu = cpu_init(cpu_model);
> > + CPUState *new_cpu = cpu_create(cpu_type);
> > CPUArchState *new_env = new_cpu->env_ptr;
> > CPUBreakpoint *bp;
> > CPUWatchpoint *wp;
> > @@ -4362,7 +4363,17 @@ int main(int argc, char **argv, char **envp)
> > tcg_exec_init(0);
> > /* NOTE: we need to init the CPU at this stage to get
> > qemu_host_page_size */
> > +
> > +#ifdef CPU_RESOLVING_TYPE
> > + cpu_type = cpu_parse_cpu_model(CPU_RESOLVING_TYPE, cpu_model);
> > + if (!cpu_type) {
> > + exit(1);
> > + }
> > + cpu_create(cpu_type);
> > +#else
> > cpu = cpu_init(cpu_model);
> > + cpu_type = object_class_get_name(object_get_class(OBJECT(cpu)));
>
> Will the final version of this series require the temporary
> #ifdefs?
>
> I'd prefer to first apply patches adding the CPU_RESOLVING_TYPE
> defines and then patches adding the code without any #ifdef at
> all.
sure, it's possible to do without temporary #ifdef
> > +#endif
> > env = cpu->env_ptr;
> > cpu_reset(cpu);
> >
> > --
> > 2.7.4
> >
>
next prev parent reply other threads:[~2018-01-19 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 17:33 [Qemu-devel] [RFC v2 0/5] generalize parsing of cpu_model (part 4) Igor Mammedov
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 [this message]
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=20180119112423.683a73ef@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).