Re: [Qemu-devel] Checking the state of arm64-linux-user

2013-10-30 Thread Michael Matz
Hi,

On Tue, 29 Oct 2013, Peter Maydell wrote:

 On 29 October 2013 18:55, Alex Bennée alex.ben...@linaro.org wrote:
  I think the problem is arm64 has been posted in several dependant patch
  sets hence working from a git tree. I think for now I'll take off the
  -Werror training wheels and see how far it gets.
 
 http://lists.nongnu.org/archive/html/qemu-devel/2013-09/msg04503.html
 
 is Alex's patchset which he rebased on to a qemu master,
 so if you can't wait for v2 then that's the one to look at.

Alex's patchset covers only the first part of the whole thing, and so 
misses some instructions and fixes.  If you merely want to use 
qemu-arm64 you're better off using the tree from me.

Alex B.: I'm building that tree with gcc 4.7 and this config:
% ../configure --disable-system --enable-linux-user --disable-werror \
  --static --disable-linux-aio --disable-strip \
  --target-list=arm64-linux-user
% make


Ciao,
Michael.

[Qemu-devel] Checking the state of arm64-linux-user

2013-10-29 Thread Alex Bennée
Hi Michael,

I'm currently at Linaro Connect and am looking at running the arm64
stuff through Peter's risu tool and getting an idea of the instruction
coverage. Alex pointed me to:

https://github.com/susematz/qemu/tree/aarch64-1.6

Which I've been looking at building. I'm hitting a bunch of issues while
building. They are mostly -Werror bits and pieces which I can work
through but as it doesn't build with the default QEMU build options I
thought I'd better check if that is the correct latest/greatest version
of the patch set.

Regards,

-- 
Alex Bennée




Re: [Qemu-devel] Checking the state of arm64-linux-user

2013-10-29 Thread Peter Maydell
On 29 October 2013 18:20, Alex Bennée alex.ben...@linaro.org wrote:
 I'm currently at Linaro Connect and am looking at running the arm64
 stuff through Peter's risu tool and getting an idea of the instruction
 coverage. Alex pointed me to:

 https://github.com/susematz/qemu/tree/aarch64-1.6

 Which I've been looking at building. I'm hitting a bunch of issues while
 building. They are mostly -Werror bits and pieces which I can work
 through but as it doesn't build with the default QEMU build options I
 thought I'd better check if that is the correct latest/greatest version
 of the patch set.

With my upstream-qemu-arm-maintainer hat on, I would suggest that
the thing we should be building and testing is the most recent set of
patches that has been submitted to the mailing list. I think Alex said
doing a v2 of that is on his todo list...

-- PMM



Re: [Qemu-devel] Checking the state of arm64-linux-user

2013-10-29 Thread Alex Bennée

peter.mayd...@linaro.org writes:

 On 29 October 2013 18:20, Alex Bennée alex.ben...@linaro.org wrote:
 I'm currently at Linaro Connect and am looking at running the arm64
 stuff through Peter's risu tool and getting an idea of the instruction
 coverage. Alex pointed me to:

 https://github.com/susematz/qemu/tree/aarch64-1.6

snip
 With my upstream-qemu-arm-maintainer hat on, I would suggest that
 the thing we should be building and testing is the most recent set of
 patches that has been submitted to the mailing list. I think Alex said
 doing a v2 of that is on his todo list...
snip

I think the problem is arm64 has been posted in several dependant patch
sets hence working from a git tree. I think for now I'll take off the
-Werror training wheels and see how far it gets.

However if you have any pointers to patchwork I can build a tree from
there as well.

-- 
Alex Bennée




Re: [Qemu-devel] Checking the state of arm64-linux-user

2013-10-29 Thread Peter Maydell
On 29 October 2013 18:55, Alex Bennée alex.ben...@linaro.org wrote:
 I think the problem is arm64 has been posted in several dependant patch
 sets hence working from a git tree. I think for now I'll take off the
 -Werror training wheels and see how far it gets.

http://lists.nongnu.org/archive/html/qemu-devel/2013-09/msg04503.html

is Alex's patchset which he rebased on to a qemu master,
so if you can't wait for v2 then that's the one to look at.

-- PMM