Re: [PATCH] target/ppc: Fix e6500 boot

2022-01-11 Thread ma...@locati.it
>From: "Cédric Le Goater" c...@kaod.org >To: "ma...@locati.it" ma...@locati.it, bala...@eik.bme.hu >Cc: faro...@linux.ibm.com, qemu-devel@nongnu.org, qemu-...@nongnu.org, >danielhb...@gmail.com >Date: Mon, 10 Jan 2022 09:04:39 +0100 >Subject: Re: [PATCH] tar

Re: [PATCH] target/ppc: Fix e6500 boot

2022-01-10 Thread Cédric Le Goater
Hello Mario, I have tried to launch a freshly compiled qemu from git master on a NXP T2080RDB devkit that has a e6500 CPU in combination with a freshly compiled kernel 5.16-rc6 I have Debian SID ppc64 up and running using such a kernel, and when I launch qemu to run a VM with the same debian

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-28 Thread ma...@locati.it
>From: "Fabiano Rosas" faro...@linux.ibm.com >To: "ma...@locati.it" ma...@locati.it, c...@kaod.org >Cc: danielhb...@gmail.com, qemu-...@nongnu.org, qemu-devel@nongnu.org, >bala...@eik.bme.hu >Date: Mon, 27 Dec 2021 17:05:46 -0300 >Subject: Re: [PA

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-27 Thread BALATON Zoltan
On Mon, 27 Dec 2021, Fabiano Rosas wrote: "ma...@locati.it" writes: I have updated  the guest VM but I get exactly the same result except that now I have libc-2.33.so installed. [...] VFS: Mounted root (ext4 filesystem) on device 254:0. devtmpfs: mounted Freeing unused kernel image (initmem)

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-27 Thread BALATON Zoltan
Hello, On Mon, 27 Dec 2021, ma...@locati.it wrote: I have updated  the guest VM but I get exactly the same result except that now I have libc-2.33.so installed. [...] VFS: Mounted root (ext4 filesystem) on device 254:0. devtmpfs: mounted Freeing unused kernel image (initmem) memory: 468K This

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-27 Thread Fabiano Rosas
"ma...@locati.it" writes: > I have updated  the guest VM but I get exactly the same result except that > now I have libc-2.33.so installed. > > [...] > VFS: Mounted root (ext4 filesystem) on device 254:0. > devtmpfs: mounted > Freeing unused kernel image (initmem) memory: 468K > This architectur

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-27 Thread ma...@locati.it
From: "Cédric Le Goater" c...@kaod.org To: "BALATON Zoltan" bala...@eik.bme.hu,"ma...@locati.it" ma...@locati.it Cc: faro...@linux.ibm.com, qemu-devel@nongnu.org, qemu-...@nongnu.org, danielhb...@gmail.com Date: Sun, 26 Dec 2021 18:57:54 +0100 Subject: Re: [PAT

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-26 Thread Cédric Le Goater
On 12/25/21 22:53, BALATON Zoltan wrote: On Sat, 25 Dec 2021, ma...@locati.it wrote: I have tried to launch a freshly compiled qemu from git master on a NXP T2080RDB devkit that has a e6500 CPU in combination with a freshly compiled kernel 5.16-rc6 I have Debian SID ppc64 up and running using

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-25 Thread BALATON Zoltan
On Sat, 25 Dec 2021, ma...@locati.it wrote: I have tried to launch a freshly compiled qemu from git master on a NXP T2080RDB devkit that has a e6500 CPU in combination with a freshly compiled kernel 5.16-rc6 I have Debian SID ppc64 up and running using such a kernel, and when I launch qemu to r

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-25 Thread ma...@locati.it
From: "BALATON Zoltan" bala...@eik.bme.hu To: "Fabiano Rosas" faro...@linux.ibm.com Cc: qemu-devel@nongnu.org, qemu-...@nongnu.org, c...@kaod.org, danielhb...@gmail.com, ma...@locati.it Date: Mon, 13 Dec 2021 20:51:15 +0100 (CET) Subject: Re: [PATCH] target/ppc: Fix e6500 b

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-15 Thread Cédric Le Goater
On 12/13/21 14:35, Fabiano Rosas wrote: When Altivec support was added to the e6500 kernel in 2012[1], the QEMU code was not changed, so we don't register the VPU/VPUA exceptions for the e6500: qemu: fatal: Raised an exception without defined vector 73 Note that the error message says 73, in

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-13 Thread BALATON Zoltan
On Mon, 13 Dec 2021, Fabiano Rosas wrote: When Altivec support was added to the e6500 kernel in 2012[1], the QEMU code was not changed, so we don't register the VPU/VPUA exceptions for the e6500: qemu: fatal: Raised an exception without defined vector 73 Note that the error message says 73, in

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-13 Thread Fabiano Rosas
Cédric Le Goater writes: > On 12/13/21 14:35, Fabiano Rosas wrote: >> When Altivec support was added to the e6500 kernel in 2012[1], the >> QEMU code was not changed, so we don't register the VPU/VPUA >> exceptions for the e6500: >> >>qemu: fatal: Raised an exception without defined vector 7

Re: [PATCH] target/ppc: Fix e6500 boot

2021-12-13 Thread Cédric Le Goater
On 12/13/21 14:35, Fabiano Rosas wrote: When Altivec support was added to the e6500 kernel in 2012[1], the QEMU code was not changed, so we don't register the VPU/VPUA exceptions for the e6500: qemu: fatal: Raised an exception without defined vector 73 Note that the error message says 73, in

[PATCH] target/ppc: Fix e6500 boot

2021-12-13 Thread Fabiano Rosas
When Altivec support was added to the e6500 kernel in 2012[1], the QEMU code was not changed, so we don't register the VPU/VPUA exceptions for the e6500: qemu: fatal: Raised an exception without defined vector 73 Note that the error message says 73, instead of 32, which is the IVOR for VPU. Thi