All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: david@redhat.com, cohuck@redhat.com, qemu-s390x@nongnu.org
Subject: [Qemu-devel] [PATCH for-4.1 0/6] target/s390x: Clean up tcg exceptions
Date: Mon,  1 Apr 2019 17:29:05 +0700	[thread overview]
Message-ID: <20190401102911.8685-1-richard.henderson@linaro.org> (raw)

I've been cleaning up some random branches and found this,
dating from mid-2017(!)  My memory is that I wrote this going
into some softfreeze and then failed to do anything with it
once development opened again.  Oops.

The major change is to handle ILEN via TCG unwinding, so that
we don't have to Just Know about the ILEN (the majority of the
calls to s390_program_interrupt use constants), or re-read from
memory (which gets EX wrong).


r~


Richard Henderson (6):
  target/s390x: Truncate 32-bit psw_addr before creating TB
  target/s390x: Add ilen to unwind data
  target/s390x: Use ilen from unwind in tlb_fill
  target/s390x: Remove ilen parameter from tcg_s390_program_interrupt
  target/s390x: Remove ilen parameter from s390_program_interrupt
  target/s390x: Use tcg_s390_program_interrupt in TCG helpers

 target/s390x/cpu.h           | 33 +++++++++++++-------
 target/s390x/internal.h      |  2 +-
 target/s390x/tcg_s390x.h     |  4 +--
 hw/s390x/s390-pci-inst.c     | 58 ++++++++++++++++++------------------
 target/s390x/cc_helper.c     |  4 +--
 target/s390x/crypto_helper.c |  7 ++---
 target/s390x/diag.c          | 14 ++++-----
 target/s390x/excp_helper.c   | 10 +++----
 target/s390x/fpu_helper.c    |  6 ++--
 target/s390x/int_helper.c    | 15 +++++-----
 target/s390x/interrupt.c     | 12 ++++----
 target/s390x/ioinst.c        | 40 ++++++++++++-------------
 target/s390x/mem_helper.c    | 53 +++++++++++++++++++-------------
 target/s390x/misc_helper.c   | 27 ++++++-----------
 target/s390x/tcg-stub.c      |  4 +--
 target/s390x/translate.c     | 16 +++++-----
 16 files changed, 163 insertions(+), 142 deletions(-)

-- 
2.17.1

             reply	other threads:[~2019-04-01 10:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 10:29 Richard Henderson [this message]
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 1/6] target/s390x: Truncate 32-bit psw_addr before creating TB Richard Henderson
2019-04-01 12:13   ` David Hildenbrand
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 2/6] target/s390x: Add ilen to unwind data Richard Henderson
2019-04-01 12:21   ` David Hildenbrand
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 3/6] target/s390x: Use ilen from unwind in tlb_fill Richard Henderson
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 4/6] target/s390x: Remove ilen parameter from tcg_s390_program_interrupt Richard Henderson
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 5/6] target/s390x: Remove ilen parameter from s390_program_interrupt Richard Henderson
2019-04-01 10:29 ` [Qemu-devel] [PATCH for-4.1 6/6] target/s390x: Use tcg_s390_program_interrupt in TCG helpers Richard Henderson
2019-04-01 12:17   ` David Hildenbrand
2019-04-01 10:39 ` [Qemu-devel] [PATCH for-4.1 0/6] target/s390x: Clean up tcg exceptions no-reply

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=20190401102911.8685-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.