qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: [Qemu-devel] [PULL] qemu-sparc update
Date: Sat, 16 Jan 2016 12:41:15 +0000	[thread overview]
Message-ID: <20160116124115.GB14747@kentang.lan> (raw)

Hi Peter,

This is simply your VMStateDescription patchset for SPARC with appropriate
SoBs added. Please pull.


ATB,

Mark.


The following changes since commit 5a57acb66f19ee52723aa05b8afbbc41c3e9ec99:

  Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20160115' into staging (2016-01-15 15:49:43 +0000)

are available in the git repository at:


  https://github.com/mcayland/qemu.git tags/qemu-sparc-signed

for you to fetch changes up to 6d5322442a6904fef51a409ec40f2945581220d6:

  target-sparc: Migrate CWP and PIL for SPARC64 (2016-01-16 12:01:23 +0000)

----------------------------------------------------------------
qemu-sparc update

----------------------------------------------------------------
Juan Quintela (4):
      vmstate: introduce CPU_DoubleU arrays
      vmstate: Introduce VMSTATE_VARRAY_MULTPLY
      vmstate: define vmstate_info_uinttl
      target-sparc: Convert to VMStateDescription

Peter Maydell (4):
      target-sparc: Split cpu_put_psr into side-effect and no-side-effect parts
      target-sparc: Don't flush TLB in cpu_load function
      target-sparc: Use VMState arrays for SPARC64 TLB/MMU state
      target-sparc: Migrate CWP and PIL for SPARC64

 hw/sparc64/sun4u.c          |   24 ---
 include/hw/hw.h             |    2 +
 include/migration/vmstate.h |   18 +++
 migration/vmstate.c         |   27 ++++
 target-sparc/cpu-qom.h      |    4 +
 target-sparc/cpu.c          |    1 +
 target-sparc/cpu.h          |    7 +-
 target-sparc/machine.c      |  370 ++++++++++++++++++++-----------------------
 target-sparc/win_helper.c   |   19 ++-
 9 files changed, 236 insertions(+), 236 deletions(-)

             reply	other threads:[~2016-01-16 12:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 12:41 Mark Cave-Ayland [this message]
2016-01-18 13:38 ` [Qemu-devel] [PULL] qemu-sparc update Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2017-10-31 17:50 Mark Cave-Ayland
2017-11-02 10:10 ` Peter Maydell
2017-04-21 19:17 Mark Cave-Ayland
2017-04-24  9:48 ` Peter Maydell
2016-06-24 17:41 Mark Cave-Ayland
2016-06-27 10:48 ` Peter Maydell
2016-06-20 21:06 Mark Cave-Ayland
2016-06-21 11:58 ` Peter Maydell
2016-04-15  8:40 Mark Cave-Ayland
2016-04-15 10:26 ` Peter Maydell
2016-04-11 15:39 Mark Cave-Ayland
2016-04-11 16:10 ` Peter Maydell
2016-01-07 12:24 Mark Cave-Ayland
2016-01-07 13:19 ` Mark Cave-Ayland
2015-03-04  6:20 Mark Cave-Ayland
2015-03-08  9:47 ` Peter Maydell
2015-03-08 10:04   ` Mark Cave-Ayland
2015-03-08 10:31     ` Peter Maydell
2015-03-08 10:57       ` Mark Cave-Ayland
2015-03-08 20:48         ` Alexander Graf
2015-03-08 21:03           ` Mark Cave-Ayland
2015-03-08 21:05             ` Alexander Graf
2015-03-09  9:32               ` Mark Cave-Ayland
2015-01-21 17:06 Mark Cave-Ayland
2015-01-22 12:13 ` Peter Maydell
2014-09-23 22:11 Mark Cave-Ayland
2014-09-24 13:30 ` Peter Maydell
2014-09-09  5:25 Mark Cave-Ayland
2014-09-09 15:15 ` 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=20160116124115.GB14747@kentang.lan \
    --to=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).