From: Greg Kurz <groug@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH v4 0/5] ppc: compute cpu_dt_id in the machine code
Date: Tue, 12 Jul 2016 14:07:28 +0200 [thread overview]
Message-ID: <20160712140728.10b98759@bahia.lan> (raw)
In-Reply-To: <146832207067.11501.8996105026000788188.stgit@bahia.lan>
On Tue, 12 Jul 2016 13:14:30 +0200
Greg Kurz <groug@kaod.org> wrote:
> Here's the current patchset I have before I go on vacation, in case it is
> needed. It is nearly the same as v3: I've just dropped patches that received
> a negative review, fixed a bug and rebased.
>
> The patches are also available here:
>
> git://github.com/gkurz/qemu.git ppc-vcpu-dt-id-rework
>
> Cheers.
>
Ugh I've fumbled *again*... I'll repost shortly.
> ---
>
> Greg Kurz (5):
> ppc: different creation paths for cpus in system and user mode
> ppc: parse cpu features once
> ppc: open code cpu creation for machine types
> ppc: each machine type to provide vcpu_dt_id
> ppc: drop vcpu_idt_id bits from the target code
>
>
> hw/ppc/e500.c | 4 ++-
> hw/ppc/mac_newworld.c | 3 +-
> hw/ppc/mac_oldworld.c | 3 +-
> hw/ppc/ppc.c | 64 +++++++++++++++++++++++++++++++++++++++++++
> hw/ppc/ppc440_bamboo.c | 3 +-
> hw/ppc/ppc4xx_devs.c | 3 +-
> hw/ppc/prep.c | 3 +-
> hw/ppc/spapr.c | 7 ++++-
> hw/ppc/spapr_cpu_core.c | 7 +++--
> hw/ppc/virtex_ml507.c | 3 +-
> include/hw/ppc/ppc.h | 2 +
> target-ppc/cpu.h | 5 ++-
> target-ppc/translate_init.c | 20 -------------
> 13 files changed, 95 insertions(+), 32 deletions(-)
>
> --
> Greg
>
>
prev parent reply other threads:[~2016-07-12 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 11:14 [Qemu-devel] [PATCH v4 0/5] ppc: compute cpu_dt_id in the machine code Greg Kurz
2016-07-12 11:15 ` [Qemu-devel] [PATCH v4 1/5] ppc: different creation paths for cpus in system and user mode Greg Kurz
2016-07-12 11:16 ` [Qemu-devel] [PATCH v4 2/5] ppc: parse cpu features once Greg Kurz
2016-07-12 12:07 ` Greg Kurz [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=20160712140728.10b98759@bahia.lan \
--to=groug@kaod.org \
--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).