[Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[John Rigby]

Resubmission of patches submitted by Alexander Graf in March.
Addressing feedback sent.

Changes in v2:
All: Use aarch64 instead of arm64 (in all case combinations).
Patch 2/12 ARM: Prepare translation for AArch64 code
- Remove uses of is_a64 that are not needed because arch choice happens at
a higher level.
- aarch64 register arrays now only have 31 entries with sp and xzr treated as
special cases.
Patch 3/12 ARM: Add AArch64 translation stub
- Remove uses of is_a64 that are not needed because arch choice happens at
a higher level.
- aarch64 register arrays now only have 31 entries with sp and xzr treated as
special cases.
Patch 7/12 linux-user: AArch64 requires at least 3.8.0
- Moved to 12/12 to appear after aarch64 is added to configure

Alexander Graf (11):
  ARM: Export cpu_env
  ARM: Prepare translation for AArch64 code
  ARM: Add AArch64 translation stub
  AArch64: Add gdb stub
  linux-user: Don't treat aarch64 cpu names specially
  linux-user: AArch64 requires at least 3.8.0
  linux-user: Add syscall handling for AArch64
  linux-user: Fix up AArch64 syscall handlers
  linux-user: Add AArch64 support
  ARM: Add aarch64 target to configure
  linux-user: AArch64 requires at least 3.8.0

Andreas Schwab (1):
  linux-user: Add signal handling for AArch64

 configure                              |    9 +
 default-configs/aarch64-linux-user.mak |    3 +
 gdb-xml/aarch64-core.xml               |   46 +++++
 gdb-xml/aarch64-fpu.xml                |   86 +++++++++
 gdbstub.c                              |   53 ++++++
 include/elf.h                          |    2 +
 linux-user/Makefile.objs               |    1 +
 linux-user/arm/syscall.h               |   46 ++++-
 linux-user/arm/syscall_nr.h            |  326 ++++++++++++++++++++++++++++++++
 linux-user/arm/target_signal.h         |    4 +
 linux-user/cpu-uname.c                 |    3 +-
 linux-user/elfload.c                   |   15 +-
 linux-user/main.c                      |   24 +++
 linux-user/signal.c                    |  263 ++++++++++++++++++++++++++
 linux-user/syscall.c                   |   10 +-
 linux-user/syscall_defs.h              |   28 ++-
 target-arm/Makefile.objs               |    1 +
 target-arm/cpu.h                       |  158 +++++++++++-----
 target-arm/translate-a64.c             |  139 ++++++++++++++
 target-arm/translate.c                 |   25 ++-
 target-arm/translate.h                 |    8 +
 21 files changed, 1186 insertions(+), 64 deletions(-)
 create mode 100644 default-configs/aarch64-linux-user.mak
 create mode 100644 gdb-xml/aarch64-core.xml
 create mode 100644 gdb-xml/aarch64-fpu.xml
 create mode 100644 target-arm/translate-a64.c

-- 
1.7.9.5

Re: [Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[Alexander Graf]

On 30.04.2013, at 08:35, John Rigby wrote:

> Resubmission of patches submitted by Alexander Graf in March.
> Addressing feedback sent.

Your mail chaining is broken :)


Alex

Re: [Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[John Rigby]

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

On Tue, Apr 30, 2013 at 3:37 AM, Alexander Graf <agraf@suse.de> wrote:

>
> On 30.04.2013, at 08:35, John Rigby wrote:
>
> > Resubmission of patches submitted by Alexander Graf in March.
> > Addressing feedback sent.
>
> Your mail chaining is broken :)
>
> yes, I see that.  When I ran git format-patch I gave it --in-reply-to='<
1362535280-5068-1-git-send-email-agraf@suse.de>' which was the msgid of
your original part 0/12.  That obviously was not the right thing.  Do I
send each part with --in-reply-to set to previous version of that patch?

--john

[-- Attachment #2: Type: text/html, Size: 1085 bytes --]

Re: [Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[Peter Maydell]

On 30 April 2013 13:58, John Rigby <john.rigby@linaro.org> wrote:
> On Tue, Apr 30, 2013 at 3:37 AM, Alexander Graf <agraf@suse.de> wrote:
>> Your mail chaining is broken :)
>>
> yes, I see that.  When I ran git format-patch I gave it
> --in-reply-to='<1362535280-5068-1-git-send-email-agraf@suse.de>' which was
> the msgid of your original part 0/12.  That obviously was not the right
> thing.  Do I send each part with --in-reply-to set to previous version of
> that patch?

You don't need to chain a v2 patch series to the previously
submitted version at all. Just make sure that each patch
in the series is a reply to its own cover letter. I use:

 git format-patch -o ~/sent-patches/whatever.2 master --cover-letter
     --subject-prefix='PATCH v2'
 [Edit the cover letter here]
 git send-email --no-chain-reply-to --to=qemu-devel@nongnu.org
     ~/sent-patches/whatever.2

(add --suppress-cc, --from, --cc, etc to taste, and you can
set these defaults in your .gitconfig rather than using command
line arguments. --dry-run is also a useful send-email option.)

PS: for Linaro you should include '--cc=patches@linaro.org' :-)

-- PMM

Re: [Qemu-devel] [PATCH v2 00/12] AArch64 preparation patch set

[Richard Henderson]

On 2013-04-30 14:15, Peter Maydell wrote:
> (add --suppress-cc, --from, --cc, etc to taste, and you can
> set these defaults in your .gitconfig rather than using command
> line arguments. --dry-run is also a useful send-email option.)

Also helpful is setting some defaults in your qemu/.git/config.

E.g. I have the --to=qemu-devel set there.  All that's required
is that you run the git-send-email from within the qemu source tree.


r~