qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PULL v2 00/18] target/microblaze patch queue
Date: Mon,  7 Sep 2020 13:04:21 -0700	[thread overview]
Message-ID: <20200907200421.186121-1-richard.henderson@linaro.org> (raw)

Doing the PR on request from Edgar.

Version 1 conflicted with a PR from thuth;
patch 1 has already been merged.


r~


The following changes since commit e11bd71f89649da3cff439c030d2ccac0cc914e3:

  Merge remote-tracking branch 'remotes/huth-gitlab/tags/pull-request-2020-09-07' into staging (2020-09-07 16:51:00 +0100)

are available in the Git repository at:

  https://github.com/rth7680/qemu.git tags/pull-mb-20200907-2

for you to fetch changes up to 7df61837df419740963f020d7ee7b852f6401301:

  configure: Do not set TARGET_ABI32 for microblaze (2020-09-07 12:58:08 -0700)

----------------------------------------------------------------
Use lookup_and_goto_tb.
Cleanup and fill in VMStateDescription.

----------------------------------------------------------------
Richard Henderson (18):
      target/microblaze: Renumber D_FLAG
      target/microblaze: Cleanup mb_cpu_do_interrupt
      target/microblaze: Rename mmu structs
      target/microblaze: Rename DISAS_UPDATE to DISAS_EXIT
      target/microblaze: Introduce DISAS_EXIT_NEXT, DISAS_EXIT_JUMP
      target/microblaze: Replace cpustate_changed with DISAS_EXIT_NEXT
      target/microblaze: Handle DISAS_EXIT_NEXT in delay slot
      target/microblaze: Force rtid, rted, rtbd to exit
      target/microblaze: Use tcg_gen_lookup_and_goto_ptr
      target/microblaze: Diagnose invalid insns in delay slots
      target/microblaze: Split out MicroBlazeCPUConfig
      target/microblaze: Reorg MicroBlazeCPUConfig to minimize holes
      target/microblaze: Move pvr regs to MicroBlazeCPUConfig
      target/microblaze: Treat pvr_regs as constant
      target/microblaze: Move mmu parameters to MicroBlazeCPUConfig
      target/microblaze: Fill in VMStateDescription for cpu
      target/microblaze: Put MicroBlazeCPUConfig into DisasContext
      configure: Do not set TARGET_ABI32 for microblaze

 configure                           |   1 -
 target/microblaze/cpu.h             |  78 +++++++------
 target/microblaze/mmu.h             |  20 +---
 hw/microblaze/petalogix_ml605_mmu.c |   6 +-
 target/microblaze/cpu.c             | 109 +++++++++---------
 target/microblaze/gdbstub.c         |   6 +-
 target/microblaze/helper.c          | 217 ++++++++++++++++--------------------
 target/microblaze/machine.c         | 106 ++++++++++++++++++
 target/microblaze/mmu.c             |  39 ++++---
 target/microblaze/op_helper.c       |   2 +-
 target/microblaze/translate.c       | 194 +++++++++++++++++++++-----------
 target/microblaze/meson.build       |   5 +-
 12 files changed, 463 insertions(+), 320 deletions(-)
 create mode 100644 target/microblaze/machine.c


             reply	other threads:[~2020-09-07 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07 20:04 Richard Henderson [this message]
2020-09-08 15:17 ` [PULL v2 00/18] target/microblaze patch queue 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=20200907200421.186121-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --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).