From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
christoffer.dall@linaro.org
Subject: Re: [PATCH kvm-unit-tests 00/15] arm64: initial drop
Date: Tue, 06 Jan 2015 09:03:40 +0000 [thread overview]
Message-ID: <87a91wnuvn.fsf@linaro.org> (raw)
In-Reply-To: <20150102174613.GA17091@hawk.usersys.redhat.com>
Andrew Jones <drjones@redhat.com> writes:
> On Fri, Dec 12, 2014 at 01:44:52PM +0100, Paolo Bonzini wrote:
<snip>
>> On 10/12/2014 20:59, Andrew Jones wrote:
>> > This series adds support for aarch64 to the kvm-unit-tests framework,
>> > bringing it to the same level as the arm support. In the process a
>> > few tweaks to the arm support were made, as one of the main goals
>> > was to share as much code as possible between the two.
>> >
>> > Patches
>> > 01 : A fix for the script runner. We need this one for arm
>> > regardless of the aarch64 support.
>> > 02-03: Fixes to the arm support. The bugs fixed weren't visible
>> > until running on aarch64.
>> > 04-07: Prep the arm framework for the bare minimal initial drop
>> > 08 : The bare minimal initial drop
>> > 09 : Add vector support to the minimal drop
>> > 10-12: Prep the arm framework for enabling the mmu on aarch64
>> > 13-14: Prep the aarch64 framework for enabling the mmu
>> > 15 : Enables the mmu on aarch64
>> >
>> > These patches are also available here
>> > https://github.com/rhdrjones/kvm-unit-tests/tree/arm64/initial-drop
<snip>
>
> Ping? I'd like to send more patches building on this series soon.
> Hopefully others (/me looks at Alex Bennee) do too :-)
I am looking at them now.
--
Alex Bennée
prev parent reply other threads:[~2015-01-06 9:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 19:59 [PATCH kvm-unit-tests 00/15] arm64: initial drop Andrew Jones
2014-12-10 19:59 ` [PATCH 01/15] arm: fix run script testdev probing Andrew Jones
2014-12-10 19:59 ` [PATCH 02/15] virtio: don't use size_t Andrew Jones
2014-12-10 19:59 ` [PATCH 03/15] arm: setup: fix type mismatch Andrew Jones
2014-12-10 19:59 ` [PATCH 04/15] Makefile: cscope may need to look in lib/$ARCH Andrew Jones
2014-12-10 19:59 ` [PATCH 05/15] arm: use absolute headers Andrew Jones
2014-12-10 19:59 ` [PATCH 06/15] arm: setup: drop unused arguments Andrew Jones
2014-12-10 20:00 ` [PATCH 07/15] arm: selftest: rename svc mode to kernel mode Andrew Jones
2014-12-10 20:00 ` [PATCH 08/15] arm64: initial drop Andrew Jones
2014-12-10 20:00 ` [PATCH 09/15] arm64: vectors support Andrew Jones
2014-12-10 20:00 ` [PATCH 10/15] arm: get PHYS_MASK from pgtable-hwdef.h Andrew Jones
2014-12-10 20:00 ` [PATCH 11/15] arm: import more linux page table api Andrew Jones
2014-12-10 20:00 ` [PATCH 12/15] arm: prepare mmu code for arm64 Andrew Jones
2014-12-10 20:00 ` [PATCH 13/15] arm64: import some Linux page table API Andrew Jones
2014-12-10 20:00 ` [PATCH 14/15] arm64: prepare for 64k pages Andrew Jones
2014-12-10 20:00 ` [PATCH 15/15] arm64: enable mmu Andrew Jones
2014-12-12 12:44 ` [PATCH kvm-unit-tests 00/15] arm64: initial drop Paolo Bonzini
2015-01-02 17:46 ` Andrew Jones
2015-01-03 8:54 ` Paolo Bonzini
2015-01-06 9:03 ` Alex Bennée [this message]
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=87a91wnuvn.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=pbonzini@redhat.com \
/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