kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Cc: thuth@redhat.com, dgibson@redhat.com,
	david@gibson.dropbear.id.au, agraf@suse.de, lvivier@redhat.com
Subject: Re: [kvm-unit-tests PATCH v2 00/14] ppc64: initial drop
Date: Wed, 10 Feb 2016 15:27:09 +0100	[thread overview]
Message-ID: <56BB48BD.2040305@redhat.com> (raw)
In-Reply-To: <1454957594-30601-1-git-send-email-drjones@redhat.com>



On 08/02/2016 19:53, Andrew Jones wrote:
> It's been a loooong time since I posted v1 of this series, but thanks
> to Thomas' poking, and even volunteering to help move v2 along, I've
> finally picked it back up.
> 
> v2:
>   Besides rebasing on latest master, v2 addresses all of David's comments
>     - assembler cleanup
>     - jump into the RTAS blob we get from DT, instead of reproducing it
>     - don't store the RTAS root node, always hunt it down
> 
>   v2 didn't address debug-exit, and we still need a solution for that.
>   Plugging chr-testdev into an spapr vty is probably what we should
>   investigate first (as was suggested by Alex Graf under the v1 review).
>   For this v2 I just kept the hack from v1, but simplified it and
>   explicitly call it out as the hack that it is.
> 
> Additional known issues:
>   Latest F22 cross-compiler (gcc5 based) doesn't generate working
>   code with this series. I didn't try to debug. The 4.9 based compiler
>   I initially used on v1 works, so I reverted to that one.
> 
> Testing:
>   I only tested with qemu-system-ppc64 (latest) on x86_64 so far. I'll
>   try to get a machine to test with real hardware (and KVM) unless
>   someone (hi Thomas :-) beats me to it.
> 
> Standard cover-letter summary:
>   This series brings basic setup; starts a test's C entry point, main(),
>   and printf, exit, and malloc work. Three more series should follow this
>   one which must bring; vector support, mmu support, and smp support, at
>   which point I believe the framework could just evolve with the creation
>   of unit tests.
> 
> Patches also available here
> https://github.com/rhdrjones/kvm-unit-tests/commits/ppc64/initial-drop-v2

The only request is to not include zero-size files; just leave them out
and add them as necessary.

Otherwise it's nice. :)

Paolo

  parent reply	other threads:[~2016-02-10 14:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 18:53 [kvm-unit-tests PATCH v2 00/14] ppc64: initial drop Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 01/14] lib: asm-generic: add missing casts Andrew Jones
2016-02-12 12:05   ` Thomas Huth
2016-02-12 13:58     ` Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 02/14] lib: share arm-selftest utility functions Andrew Jones
2016-02-12 12:40   ` Thomas Huth
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 03/14] config: no need to mix arch makefiles Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 04/14] powerpc/ppc64: start skeleton framework Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 05/14] powerpc/pp64: ppc-ify makefiles and linker script Andrew Jones
2016-02-09 17:54   ` [kvm-unit-tests PATCH] align toc to 256 bytes Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 06/14] powerpc/ppc64: add boot rom source Andrew Jones
2016-02-12  6:27   ` Thomas Huth
2016-02-12 10:07     ` Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 07/14] powerpc/ppc64: add bootloader to bounce into memory Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 08/14] powerpc/ppc64: add HV putchar Andrew Jones
2016-02-12 17:08   ` Thomas Huth
2016-02-12 17:45     ` Thomas Huth
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 09/14] powerpc/ppc64: adapt arm's setup Andrew Jones
2016-02-12 11:50   ` Thomas Huth
2016-02-12 13:59     ` Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 10/14] powerpc/ppc64: relocate linker VMAs Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 11/14] powerpc/ppc64: add run script and unittests.cfg Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 12/14] mkstandalone: add support for powerpc Andrew Jones
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 13/14] powerpc/ppc64: add RTAS support Andrew Jones
2016-02-12 17:51   ` Thomas Huth
2016-02-08 18:53 ` [kvm-unit-tests PATCH v2 14/14] powerpc/ppc64: HACK: make a fake debug-exit Andrew Jones
2016-02-12 18:07   ` Thomas Huth
2016-02-12 22:50     ` Paolo Bonzini
2016-02-09 17:49 ` [kvm-unit-tests PATCH v2 00/14] ppc64: initial drop Andrew Jones
2016-02-10 14:27 ` Paolo Bonzini [this message]
2016-02-11 11:56   ` Andrew Jones
2016-02-11 12:36     ` Paolo Bonzini
2016-02-11 13:36 ` Laurent Vivier
2016-02-11 15:29   ` Andrew Jones
2016-02-11 16:44     ` Laurent Vivier
2016-02-11 17:22       ` Andrew Jones
2016-02-11 17:47         ` Laurent Vivier
2016-02-12 10:06           ` Andrew Jones
2016-02-12 10:31             ` Laurent Vivier
2016-02-12 10:57               ` Andrew Jones
2016-02-12 13:44                 ` Andrew Jones
2016-02-14 22:43                   ` David Gibson

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=56BB48BD.2040305@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=dgibson@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=thuth@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;
as well as URLs for NNTP newsgroup(s).