qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andreas Schwab <schwab@suse.de>, Michael Matz <matz@suse.de>,
	Claudio Fontana <claudio.fontana@huawei.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Checking the state of arm64-linux-user
Date: Tue, 29 Oct 2013 18:55:35 +0000	[thread overview]
Message-ID: <878uxbx5y0.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA8zrMjxqrM=Wr9-A9AXz=hNrVCKzHn9CUZ2e=Pwz=t94w@mail.gmail.com>


peter.maydell@linaro.org writes:

> On 29 October 2013 18:20, Alex Bennée <alex.bennee@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

  reply	other threads:[~2013-10-29 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 18:20 [Qemu-devel] Checking the state of arm64-linux-user Alex Bennée
2013-10-29 18:26 ` Peter Maydell
2013-10-29 18:55   ` Alex Bennée [this message]
2013-10-29 18:58     ` Peter Maydell
2013-10-30 13:25       ` Michael Matz

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=878uxbx5y0.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=agraf@suse.de \
    --cc=claudio.fontana@huawei.com \
    --cc=matz@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=schwab@suse.de \
    /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).