qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Riku Voipio <riku.voipio@iki.fi>,
	Michael Tokarev <mjt@tls.msk.ru>, Alexander Graf <agraf@suse.de>,
	Greg Kurz <gkurz@linux.vnet.ibm.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user: set ppc64/ppc64le default CPU to POWER8
Date: Mon, 15 Feb 2016 13:25:26 +0000	[thread overview]
Message-ID: <CAFEAcA-HLGc-Q0CqvMtr-E8JkaCEzVhDJSJq9Dvu2_PU6t03=g@mail.gmail.com> (raw)
In-Reply-To: <1454612161-24396-1-git-send-email-lvivier@redhat.com>

On 4 February 2016 at 18:56, Laurent Vivier <lvivier@redhat.com> wrote:
> Set the default to the latest CPU version to have the
> largest set of available features.
>
> It is also really needed in little-endian mode because
> POWER7 is not really supported in this mode and some distros
> (at least debian) generate POWER8 code for their ppc64le target.
>
> Fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813698
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>

This patch is a good fix, but for the longer term is it possible
on PPC to define an "any" CPU which is the largest possible set
of usable-together userspace features? That would make it easier
for us to avoid this problem in the future for POWER9, POWER10,...

thanks
-- PMM

      parent reply	other threads:[~2016-02-15 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 18:56 [Qemu-devel] [PATCH] linux-user: set ppc64/ppc64le default CPU to POWER8 Laurent Vivier
2016-02-04 19:01 ` Alexander Graf
2016-02-04 21:24 ` Michael Tokarev
2016-02-15 13:15 ` Riku Voipio
2016-02-15 13:25 ` Peter Maydell [this message]

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='CAFEAcA-HLGc-Q0CqvMtr-E8JkaCEzVhDJSJq9Dvu2_PU6t03=g@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=agraf@suse.de \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=lvivier@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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).