qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: peter.maydell@linaro.org
Cc: agraf@suse.de, mdroth@linux.vnet.ibm.com,
	bharata@linux.vnet.ibm.com, imammedo@redhat.com,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org, groug@kaod.org,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PULL 0/5] ppc-for-2.7 queue 20160726
Date: Tue, 26 Jul 2016 13:06:06 +1000	[thread overview]
Message-ID: <1469502371-1206-1-git-send-email-david@gibson.dropbear.id.au> (raw)

The following changes since commit 2d2e632ad00d11867c6c5625605b1fbc022dd62f:

  Update version for v2.7.0-rc0 release (2016-07-22 15:32:42 +0100)

are available in the git repository at:

  git://github.com/dgibson/qemu.git tags/ppc-for-2.7-20160726

for you to fetch changes up to 12bf2d33fe520f9cfd09f7bf9d46ae3202c3cb49:

  spapr: disintricate core-id from DT semantics (2016-07-25 15:43:41 +1000)

----------------------------------------------------------------
ppc patch queue 2016-07-26

Here's the current batch of ppc and spapr related patches intended for
qemu-2.7.  Given the late stage in 2.7 development, these are all
bugfixes with one exception:

The "spapr: disintricate core-id from DT semantics" changes the way
ids are assigned in the new core-based hotplug infrastructure.  This
isn't strictly a bugfix, but we've determined that the current way of
assigning core-ids will cause considerable grief with future plans for
cpu hotplug.  Therefore it's better to fix this now, late in 2.7,
before we have a released version with the problematic numbering.

----------------------------------------------------------------
Greg Kurz (1):
      spapr: disintricate core-id from DT semantics

Michael Walle (1):
      target-ppc: add PPC_MFTB flag to e500mc and e5500

Thomas Huth (2):
      ppc: Huge page detection mechanism fixes - Episode III
      hw/ppc/spapr: Make sure to close the htab_fd when migration is canceled

lvivier@redhat.com (1):
      spapr: fix spapr-nvram migration

 hw/nvram/spapr_nvram.c      | 23 +++++++++++++++--------
 hw/ppc/spapr.c              | 19 +++++++++++++------
 hw/ppc/spapr_cpu_core.c     | 24 +++++++++++-------------
 target-ppc/kvm.c            | 27 ++++++++++++++-------------
 target-ppc/translate_init.c |  4 ++--
 5 files changed, 55 insertions(+), 42 deletions(-)

             reply	other threads:[~2016-07-26  3:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26  3:06 David Gibson [this message]
2016-07-26  3:06 ` [Qemu-devel] [PULL 1/5] ppc: Huge page detection mechanism fixes - Episode III David Gibson
2016-07-26  3:06 ` [Qemu-devel] [PULL 2/5] hw/ppc/spapr: Make sure to close the htab_fd when migration is canceled David Gibson
2016-07-26  3:06 ` [Qemu-devel] [PULL 3/5] spapr: fix spapr-nvram migration David Gibson
2016-07-26  3:06 ` [Qemu-devel] [PULL 4/5] target-ppc: add PPC_MFTB flag to e500mc and e5500 David Gibson
2016-07-26  3:06 ` [Qemu-devel] [PULL 5/5] spapr: disintricate core-id from DT semantics David Gibson
2016-07-26 11:38 ` [Qemu-devel] [PULL 0/5] ppc-for-2.7 queue 20160726 Peter Maydell

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=1469502371-1206-1-git-send-email-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=groug@kaod.org \
    --cc=imammedo@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --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).