On Fri, Jul 17, 2015 at 01:56:40PM +0200, Andrew Jones wrote:
I've started playing with adding ppc support to kvm-unit-tests,
using spapr for the machine model. I wanted to link the unit test
at 0x40 to match qemu's load address, making the unit test
startup code simpler, but ended up with
On 20/07/15 15:09, Andrew Jones wrote:
On Mon, Jul 20, 2015 at 08:47:53AM +0200, Thomas Huth wrote:
...
... or you could try to get the elf_reloc code working for POWER, too
(see include/hw/elf_ops.h). That way QEMU would take care of relocating
your program. (you can peek at
On Tue, Jul 21, 2015 at 09:10:44AM +0200, Thomas Huth wrote:
On 20/07/15 15:09, Andrew Jones wrote:
On Mon, Jul 20, 2015 at 08:47:53AM +0200, Thomas Huth wrote:
...
... or you could try to get the elf_reloc code working for POWER, too
(see include/hw/elf_ops.h). That way QEMU would take
On 20/07/15 07:01, David Gibson wrote:
On Fri, Jul 17, 2015 at 01:56:40PM +0200, Andrew Jones wrote:
I've started playing with adding ppc support to kvm-unit-tests,
using spapr for the machine model. I wanted to link the unit test
at 0x40 to match qemu's load address, making the unit test
On Mon, Jul 20, 2015 at 08:47:53AM +0200, Thomas Huth wrote:
On 20/07/15 07:01, David Gibson wrote:
On Fri, Jul 17, 2015 at 01:56:40PM +0200, Andrew Jones wrote:
I've started playing with adding ppc support to kvm-unit-tests,
using spapr for the machine model. I wanted to link the unit test
On Fri, Jul 17, 2015 at 01:56:40PM +0200, Andrew Jones wrote:
I've started playing with adding ppc support to kvm-unit-tests,
using spapr for the machine model. I wanted to link the unit test
at 0x40 to match qemu's load address, making the unit test
startup code simpler, but ended up with
I've started playing with adding ppc support to kvm-unit-tests,
using spapr for the machine model. I wanted to link the unit test
at 0x40 to match qemu's load address, making the unit test
startup code simpler, but ended up with 0x80 instead, due to
how translate_kernel_address works. The
