[Qemu-devel] [PATCH v3 0/6] arm: fixes for eret, isb and DISAS_UPDATE handling

Alex Bennée posted 6 patches 6 years, 9 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20170711175937.23140-1-alex.bennee@linaro.org
Test FreeBSD passed
Test checkpatch passed
Test docker passed
Test s390x passed
There is a newer version of this series
include/exec/exec-all.h    | 29 ++++++++++++++++++++++++++---
target/arm/translate-a64.c | 19 ++++++++++---------
target/arm/translate.c     | 22 ++++++++++++++--------
target/arm/translate.h     |  5 ++++-
4 files changed, 54 insertions(+), 21 deletions(-)
[Qemu-devel] [PATCH v3 0/6] arm: fixes for eret, isb and DISAS_UPDATE handling
Posted by Alex Bennée 6 years, 9 months ago
Hi,

Hopefully this is the final iteration after:

  https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg02452.html

The only major change is fixing up gen_goto_tb for arm and then using
that in both a32 and a64 for the ISB changes. Other than that I've
applied the review tags.

Hopefully there isn't anything else that needs fixing so I guess the
next question is who's tree should this go through?

Alex Bennée (6):
  include/exec/exec-all: document common exit conditions
  target/arm/translate: make DISAS_UPDATE match declared semantics
  target/arm/translate.h: expand comment on DISAS_EXIT
  target/arm/translate: ensure gen_goto_tb sets exit flags
  target/arm: use gen_goto_tb for ISB handling
  target/arm: use DISAS_EXIT for eret handling

 include/exec/exec-all.h    | 29 ++++++++++++++++++++++++++---
 target/arm/translate-a64.c | 19 ++++++++++---------
 target/arm/translate.c     | 22 ++++++++++++++--------
 target/arm/translate.h     |  5 ++++-
 4 files changed, 54 insertions(+), 21 deletions(-)

-- 
2.13.0


Re: [Qemu-devel] [PATCH v3 0/6] arm: fixes for eret, isb and DISAS_UPDATE handling
Posted by Richard Henderson 6 years, 9 months ago
On 07/11/2017 07:59 AM, Alex Bennée wrote:
> Hopefully there isn't anything else that needs fixing so I guess the
> next question is who's tree should this go through?

I'm happy with this going through the arm tree.


r~