From: David Hildenbrand <david@redhat.com>
To: Bruce Rogers <brogers@suse.com>, qemu-devel@nongnu.org
Cc: rth@twiddle.net, agraf@suse.de,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] linux-user: Exclude more cpu model code when building s390x linux-user
Date: Thu, 2 Mar 2017 20:50:46 +0100 [thread overview]
Message-ID: <36cb066c-4d1f-dc7f-ada6-cef224566f2d@redhat.com> (raw)
In-Reply-To: <20170302193300.21188-1-brogers@suse.com>
Am 02.03.2017 um 20:33 schrieb Bruce Rogers:
> Currently qemu-s390x segfaults. Avoid cpu model code which doesn't
> apply in linux user case.
That was also my impression, but it does apply. However, for now it
doesn't matter, as also tcg isn't properly wired up.
In general, linux-user can support _at least_ the same features as tcg,
in theory even more (all that only apply to kernel space).
We had a proper fix on this list by Richard Henderson, wonder what
happened to that?
This file should contain no CONFIG_USER_ONLY apart from the QMP
interface stuff.
> ---
> target/s390x/cpu_models.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> index 2a894eec65..97e4e75f68 100644
> --- a/target/s390x/cpu_models.c
> +++ b/target/s390x/cpu_models.c
> @@ -590,7 +590,6 @@ CpuModelBaselineInfo *arch_query_cpu_model_baseline(CpuModelInfo *infoa,
> cpu_info_from_model(baseline_info->model, &model, true);
> return baseline_info;
> }
> -#endif
>
> static void check_consistency(const S390CPUModel *model)
> {
> @@ -660,7 +659,6 @@ static void check_compatibility(const S390CPUModel *max_model,
>
> static S390CPUModel *get_max_cpu_model(Error **errp)
> {
> -#ifndef CONFIG_USER_ONLY
> static S390CPUModel max_model;
> static bool cached;
>
> @@ -680,9 +678,9 @@ static S390CPUModel *get_max_cpu_model(Error **errp)
> cached = true;
> return &max_model;
> }
> -#endif
> return NULL;
> }
> +#endif
>
> static inline void apply_cpu_model(const S390CPUModel *model, Error **errp)
> {
> @@ -718,6 +716,7 @@ static inline void apply_cpu_model(const S390CPUModel *model, Error **errp)
>
> void s390_realize_cpu_model(CPUState *cs, Error **errp)
> {
> +#ifndef CONFIG_USER_ONLY
> S390CPUClass *xcc = S390_CPU_GET_CLASS(cs);
> S390CPU *cpu = S390_CPU(cs);
> const S390CPUModel *max_model;
> @@ -751,6 +750,7 @@ void s390_realize_cpu_model(CPUState *cs, Error **errp)
> }
>
> apply_cpu_model(cpu->model, errp);
> +#endif
> }
>
> static void get_feature(Object *obj, Visitor *v, const char *name,
>
--
Thanks,
David
next prev parent reply other threads:[~2017-03-02 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 19:33 [Qemu-devel] [PATCH] linux-user: Exclude more cpu model code when building s390x linux-user Bruce Rogers
2017-03-02 19:50 ` David Hildenbrand [this message]
2017-03-02 19:53 ` David Hildenbrand
2017-03-02 19:59 ` Bruce Rogers
2017-03-02 20:03 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 19:51 Bruce Rogers
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=36cb066c-4d1f-dc7f-ada6-cef224566f2d@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=brogers@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).