On 22/05/2021 23:08, BALATON Zoltan wrote:
On Sat, 22 May 2021, Alexey Kardashevskiy wrote:
On 22/05/2021 05:57, BALATON Zoltan wrote:
On Fri, 21 May 2021, BALATON Zoltan wrote:
On Fri, 21 May 2021, Alexey Kardashevskiy wrote:
On 21/05/2021 07:59, BALATON Zoltan wrote:
On Thu, 20 May
On 23/05/2021 02:46, BALATON Zoltan wrote:
On Sat, 22 May 2021, BALATON Zoltan wrote:
On Sat, 22 May 2021, BALATON Zoltan wrote:
On Sat, 22 May 2021, Alexey Kardashevskiy wrote:
VOF itself does not prints anything in this patch.
However it seems to be needed for linux as the first thing
On 23/05/2021 01:02, BALATON Zoltan wrote:
On Sat, 22 May 2021, BALATON Zoltan wrote:
On Sat, 22 May 2021, Alexey Kardashevskiy wrote:
VOF itself does not prints anything in this patch.
However it seems to be needed for linux as the first thing it does
seems to be getting /chosen/stdout
On 22/05/2021 23:01, BALATON Zoltan wrote:
On Sat, 22 May 2021, Alexey Kardashevskiy wrote:
On 21/05/2021 19:05, BALATON Zoltan wrote:
On Fri, 21 May 2021, Alexey Kardashevskiy wrote:
On 21/05/2021 07:59, BALATON Zoltan wrote:
On Thu, 20 May 2021, Alexey Kardashevskiy wrote:
The PAPR
On 22/05/2021 05:57, BALATON Zoltan wrote:
On Fri, 21 May 2021, BALATON Zoltan wrote:
On Fri, 21 May 2021, Alexey Kardashevskiy wrote:
On 21/05/2021 07:59, BALATON Zoltan wrote:
On Thu, 20 May 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's pres
On 21/05/2021 19:05, BALATON Zoltan wrote:
On Fri, 21 May 2021, Alexey Kardashevskiy wrote:
On 21/05/2021 07:59, BALATON Zoltan wrote:
On Thu, 20 May 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hyperviso
On 21/05/2021 07:59, BALATON Zoltan wrote:
On Thu, 20 May 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hyper
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-killslof
On 18/05/2021 04:44, BALATON Zoltan wrote:
On Mon, 17 May 2021, BALATON Zoltan wrote:
On Mon, 17 May 2021, Alexey Kardashevskiy wrote:
On 5/17/21 09:34, BALATON Zoltan wrote:
On Sat, 15 May 2021, BALATON Zoltan wrote:
On Sat, 15 May 2021, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey
On 17/05/2021 22:17, BALATON Zoltan wrote:
On Mon, 17 May 2021, Alexey Kardashevskiy wrote:
On 5/16/21 01:04, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
[snip]
+/* Defined as Big Endian */
+struct prom_args {
+ uint32_t service;
+ uint32_t nargs
On 5/17/21 09:34, BALATON Zoltan wrote:
On Sat, 15 May 2021, BALATON Zoltan wrote:
On Sat, 15 May 2021, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
[snip]
+/* Defined as Big Endian */
+struct prom_args {
+ uint32_t service;
+ uint32_t nargs
On 5/16/21 01:04, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
[snip]
+/* Defined as Big Endian */
+struct prom_args {
+ uint32_t service;
+ uint32_t nargs;
+ uint32_t nret;
+ uint32_t args[10];
+} QEMU_PACKED;
This #define and struct definition
On 5/16/21 06:19, BALATON Zoltan wrote:
On Thu, 22 Apr 2021, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hyper
On 4/22/21 22:58, Alexey Kardashevskiy wrote:
The PAPR platform describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Ping? Thanks,
Since the beginning
On 4/28/21 22:33, Oliver O'Halloran wrote:
On Tue, Apr 27, 2021 at 9:56 PM Mahesh Salgaonkar wrote:
With upstream kernel, especially after commit 98ba956f6a389
("powerpc/pseries/eeh: Rework device EEH PE determination") we see that KVM
guest isn't able to enable EEH option for PCI pass-thro
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-killslof
On 4/21/21 15:27, David Gibson wrote:
On Tue, Apr 20, 2021 at 07:16:35PM +1000, Alexey Kardashevskiy wrote:
On 20/04/2021 13:14, David Gibson wrote:
Overall, looking good. I'm pretty much happy to take it into 6.1. I
do have quite a few comments below, but they're basicall
On 20/04/2021 13:14, David Gibson wrote:
Overall, looking good. I'm pretty much happy to take it into 6.1. I
do have quite a few comments below, but they're basically all just
polish.
On Wed, Mar 31, 2021 at 01:53:08PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which
On 31/03/2021 13:53, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning, the ru
On 31/03/2021 12:03, David Gibson wrote:
On Thu, Mar 25, 2021 at 02:25:33PM +1100, Alexey Kardashevskiy wrote:
On 25/03/2021 13:52, David Gibson wrote:
On Tue, Mar 23, 2021 at 01:58:30PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that&#
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-kills
SLOF instantiates RTAS since
744a928ccee9 ("spapr: Stop providing RTAS blob")
so the max address applies to the FDT only.
This renames the macro and fixes up the comment.
This should not cause any behavioral change.
Signed-off-by: Alexey Kardashevskiy
---
hw/ppc/spapr.c | 8 --
On 25/03/2021 15:40, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning, the ru
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-kills
On 25/03/2021 13:52, David Gibson wrote:
On Tue, Mar 23, 2021 at 01:58:30PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration betwee
On 22/03/2021 16:44, David Gibson wrote:
On Thu, Feb 25, 2021 at 02:23:35PM +1100, Alexey Kardashevskiy wrote:
There is no H_REGISTER_PROCESS_TABLE, it is H_REGISTER_PROC_TBL handler
for which is still called h_register_process_table() though.
Signed-off-by: Alexey Kardashevskiy
Applied
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-kills
On 10/03/2021 13:40, David Gibson wrote:
On Wed, Mar 10, 2021 at 12:55:07PM +1100, Alexey Kardashevskiy wrote:
On 10/03/2021 01:00, BALATON Zoltan wrote:
On Tue, 9 Mar 2021, Alexey Kardashevskiy wrote:
On 09/03/2021 16:29, David Gibson wrote:
+struct ClientArchitectureSupportClass
hat later on we might be adding support for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-kills
On 10/03/2021 01:00, BALATON Zoltan wrote:
On Tue, 9 Mar 2021, Alexey Kardashevskiy wrote:
On 09/03/2021 16:29, David Gibson wrote:
+struct ClientArchitectureSupportClass {
+ InterfaceClass parent;
+ target_ulong (*cas)(CPUState *cs, target_ulong vec);
+ void (*quiesce)(void);
Is
On 09/03/2021 16:29, David Gibson wrote:
+struct ClientArchitectureSupportClass {
+InterfaceClass parent;
+target_ulong (*cas)(CPUState *cs, target_ulong vec);
+void (*quiesce)(void);
Is there actually any real connection of quiesce behaviour to cas
behaviour? Basically, I'm w
On 02/03/2021 14:35, David Gibson wrote:
On Wed, Feb 24, 2021 at 04:41:30PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration betwee
There is no H_REGISTER_PROCESS_TABLE, it is H_REGISTER_PROC_TBL handler
for which is still called h_register_process_table() though.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/hw/ppc/spapr.h b
t for
booting from QEMU backends (blockdev is the first candidate) without
devices/drivers in between as OF1275 does not require that and
it is quite easy to so.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-killslof-localhost-ppc64/qemu-system-ppc6
On 23/02/2021 23:24, Christian Schoenebeck wrote:
On Dienstag, 23. Februar 2021 12:54:47 CET Peter Maydell wrote:
On Tue, 23 Feb 2021 at 11:39, Greg Kurz wrote:
On Tue, 23 Feb 2021 11:09:05 +
Peter Maydell wrote:
On Mon, 22 Feb 2021 at 14:43, Greg Kurz wrote:
My understanding is th
On 23/02/2021 14:07, David Gibson wrote:
On Tue, Feb 09, 2021 at 10:02:52PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration betwee
On 23/02/2021 16:28, David Gibson wrote:
On Tue, Feb 23, 2021 at 04:01:00PM +1100, Alexey Kardashevskiy wrote:
On 23/02/2021 14:07, David Gibson wrote:
On Tue, Feb 09, 2021 at 10:02:52PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that&#
On 23/02/2021 14:07, David Gibson wrote:
On Tue, Feb 09, 2021 at 10:02:52PM +1100, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration betwee
handy too.
On 09/02/2021 22:02, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmware and the hypervisor.
Since the beginning
changes up to 7745df3b2bc512e71badb52f8f07452260ad7409:
pseries: Update SLOF firmware image (2021-02-19 14:56:39 +1100)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin
On 27/01/2021 12:28, Alexey Kardashevskiy wrote:
On 25/01/2021 21:23, Greg Kurz wrote:
On Sat, 23 Jan 2021 13:36:34 +1100
Alexey Kardashevskiy wrote:
On 23/01/2021 04:01, Greg Kurz wrote:
It is currently not possible to perform a strict boot from USB storage:
$ qemu-system-ppc64
range in the POWERPC world, according
to POWERPC veterans; mixing styles in the firmware's .c and .s is
weird too IMO.
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
-c 0 /home/aik/pbuild/qemu-killslof-localhost-ppc64/qemu-system-ppc64 \
-nodefaults \
-chardev stdio,id=
On 25/01/2021 21:23, Greg Kurz wrote:
On Sat, 23 Jan 2021 13:36:34 +1100
Alexey Kardashevskiy wrote:
On 23/01/2021 04:01, Greg Kurz wrote:
It is currently not possible to perform a strict boot from USB storage:
$ qemu-system-ppc64 -accel kvm -nodefaults -nographic -serial stdio
idden for a long time because SLOF used to rename USB device
nodes, until this commit, merged in QEMU 4.2.0 :
commit 85164ad4ed9960cac842fa4cc067c6b6699b0994
Author: Alexey Kardashevskiy
Date: Wed Sep 11 16:24:32 2019 +1000
pseries: Update SLOF firmware image
This fixes USB host bus
On 19/12/2020 01:04, Greg Kurz wrote:
On Fri, 18 Dec 2020 13:50:40 +1100
Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmwar
ernel and initradmdisk to
boot from any possible source. Note this requires reasonably recent guest
kernel with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df5be5be8735
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
-c 0 /home/aik/pbuild/qe
On 07/12/2020 22:48, BALATON Zoltan wrote:
diff --git a/include/hw/ppc/spapr.h b/include/hw/ppc/spapr.h
index 2e89e36cfbdc..048bf49592aa 100644
--- a/include/hw/ppc/spapr.h
+++ b/include/hw/ppc/spapr.h
@@ -175,6 +175,13 @@ struct SpaprMachineState {
long kernel_size;
bool kernel_le;
On 08/12/2020 04:47, Cédric Le Goater wrote:
On 12/7/20 6:15 PM, Greg Kurz wrote:
On Mon, 7 Dec 2020 18:33:27 +1100
Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it spec
On 05/12/2020 05:32, Greg Kurz wrote:
On Tue, 13 Oct 2020 13:19:11 +1100
Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration between the firmwar
ernel and initradmdisk to
boot from any possible source. Note this requires reasonably recent guest
kernel with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df5be5be8735
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
/home/aik/pbuild/qemu-k
On 05/12/2020 05:43, Greg Kurz wrote:
On Fri, 4 Dec 2020 19:32:05 +0100
Greg Kurz wrote:
That's all for now.
Just one last item. I'm observing failures with nvram in the guest:
[root@vir76 ~]# nvram --print-config
[ 88.179444] nvram[936]: unhandled signal 11 at 7fffc83a nip
0
Has anyone at least tried this, or everybody is busy KVMforuming? :)
On 13/10/2020 13:19, Alexey Kardashevskiy wrote:
The PAPR platform which describes an OS environment that's presented by
a combination of a hypervisor and firmware. The features it specifies
require collaboration betwee
://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df5be5be8735
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
pbuild/qemu-killslof-localhost-ppc64/ppc64-softmmu/qemu-system-ppc64 \
-nodefaults \
-chardev stdio,id=STDIO0,signal=off,mux=on \
-device
On 12/10/2020 22:51, Greg Kurz wrote:
On Mon, 12 Oct 2020 13:40:33 +0200
BALATON Zoltan via wrote:
On Mon, 12 Oct 2020, Alexey Kardashevskiy wrote:
On 29/09/2020 20:35, Alexey Kardashevskiy wrote:
On 16/07/2020 23:22, David Gibson wrote:
On Thu, Jul 16, 2020 at 07:04:56PM +1000, Alexey
On 29/09/2020 20:35, Alexey Kardashevskiy wrote:
On 16/07/2020 23:22, David Gibson wrote:
On Thu, Jul 16, 2020 at 07:04:56PM +1000, Alexey Kardashevskiy wrote:
Ping? I kinda realize it is not going to replace SLOF any time soon but
still...
Yeah, I know. I just haven't had ti
On 16/07/2020 23:22, David Gibson wrote:
On Thu, Jul 16, 2020 at 07:04:56PM +1000, Alexey Kardashevskiy wrote:
Ping? I kinda realize it is not going to replace SLOF any time soon but
still...
Yeah, I know. I just haven't had time to consider it. Priority
starvation.
Still? :)
7f5258dd8327d574de455a2271788474fa25548d:
pseries: Update SLOF firmware image (2020-07-17 13:23:00 +1000)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 965112 -> 968368 by
Ping? I kinda realize it is not going to replace SLOF any time soon but
still...
On 07/07/2020 10:34, Alexey Kardashevskiy wrote:
> Ping?
>
>
> On 24/06/2020 10:28, Alexey Kardashevskiy wrote:
>> Ping?
>>
>> On 02/06/2020 21:40, Alexey Kardashevskiy wrote:
>>
Ping?
On 24/06/2020 10:28, Alexey Kardashevskiy wrote:
> Ping?
>
> On 02/06/2020 21:40, Alexey Kardashevskiy wrote:
>> Ping?
>>
>> On 13/05/2020 13:58, Alexey Kardashevskiy wrote:
>>> The PAPR platform which describes an OS environment that's presented
Ping?
On 02/06/2020 21:40, Alexey Kardashevskiy wrote:
> Ping?
>
> On 13/05/2020 13:58, Alexey Kardashevskiy wrote:
>> The PAPR platform which describes an OS environment that's presented by
>> a combination of a hypervisor and firmware. The features it specifies
>&g
Ping?
On 13/05/2020 13:58, Alexey Kardashevskiy wrote:
> The PAPR platform which describes an OS environment that's presented by
> a combination of a hypervisor and firmware. The features it specifies
> require collaboration between the firmware and the hypervisor.
>
> Sinc
Ping?
On 13/05/2020 12:43, Alexey Kardashevskiy wrote:
> The following changes since commit 83b700a441ef8303983eed16c244adde8e40e808:
>
> target/ppc: Fix arguments to ppc_radix64_partition_scoped_xlate()
> (2020-05-11 11:44:03 +1000)
>
> are available in the Git repos
://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df5be5be8735
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
pbuild/qemu-killslof-localhost-ppc64/ppc64-softmmu/qemu-system-ppc64 \
-nodefaults \
-chardev stdio,id=STDIO0,signal=off,mux=on \
-device
up to dc5e3ca3fd80048593153636020edae23cc583ac:
pseries: Update SLOF firmware image (2020-05-13 12:34:59 +1000)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin
On 05/05/2020 15:50, David Gibson wrote:
> On Tue, May 05, 2020 at 10:56:17AM +1000, Alexey Kardashevskiy wrote:
>>
>>
>> On 04/05/2020 21:30, Greg Kurz wrote:
>>> On Fri, 17 Apr 2020 14:11:05 +1000
>>> Alexey Kardashevskiy wrote:
>>>
>>&g
On 04/05/2020 21:30, Greg Kurz wrote:
> On Fri, 17 Apr 2020 14:11:05 +1000
> Alexey Kardashevskiy wrote:
>
>> At the moment the VCPU init sequence includes setting PVR which in case of
>> KVM-HV only checks if it matches the hardware PVR mask as PVR cannot be
>>
On 04/05/2020 21:38, Cédric Le Goater wrote:
>
>
> On 5/4/20 1:30 PM, Greg Kurz wrote:
>> On Fri, 17 Apr 2020 14:11:05 +1000
>> Alexey Kardashevskiy wrote:
>>
>>> At the moment the VCPU init sequence includes setting PVR which in case of
>>> KVM-
On 17/04/2020 14:11, Alexey Kardashevskiy wrote:
> At the moment the VCPU init sequence includes setting PVR which in case of
> KVM-HV only checks if it matches the hardware PVR mask as PVR cannot be
> virtualized by the hardware. In order to cope with various CPU revisions
> only
rrp)
>
> /* Some NVLink bridges may not have assigned ATSD */
> if (atsdreg->size) {
> -p = mmap(NULL, atsdreg->size, PROT_READ | PROT_WRITE | PROT_EXEC,
> +p = mmap(NULL, atsdreg->size, PROT_READ | PROT_WRITE,
This chunk is ok as ATS
by default
to preserve the existing behavior. When "off", it is the user's
responsibility to specify the correct CPU.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr.h | 5 -
hw/ppc/spapr.c | 1 +
hw/ppc/spapr_caps.c| 18 ++
ta
On 31/03/2020 18:56, Philippe Mathieu-Daudé wrote:
> On 3/31/20 5:27 AM, David Gibson wrote:
>> Currently, we can't properly handle unplug of NVLink2 devices, because we
>> don't have code to tear down their special memory resources. There's not
>> a lot of impetus to implement that: since hard
On 31/03/2020 18:08, Greg Kurz wrote:
> On Tue, 31 Mar 2020 13:59:01 +1100
> Alexey Kardashevskiy wrote:
>
>>
>>
>> On 31/03/2020 11:44, David Gibson wrote:
>>> On Wed, Mar 25, 2020 at 04:25:24PM +0100, Greg Kurz wrote:
>>>> The CAS reboot fla
x27;t
> be hot unplugged, the guest side drivers don't usually support unplug
> anyway.
>
> Therefore, simply prevent unplug of NVLink2 devices.
>
> Signed-off-by: David Gibson
Reviewed-by: Alexey Kardashevskiy
> ---
> hw/ppc/spapr_pci.c | 4
> 1 file chang
On 26/03/2020 01:41, Nicholas Piggin wrote:
> This implements the NMI interface for the PNV machine, similarly to
> commit 3431648272d ("spapr: Add support for new NMI interface") for
> SPAPR.
>
> Signed-off-by: Nicholas Piggin
> ---
> hw/ppc/pnv.c | 30 +-
> 1 fil
On 31/03/2020 11:44, David Gibson wrote:
> On Wed, Mar 25, 2020 at 04:25:24PM +0100, Greg Kurz wrote:
>> The CAS reboot flag was introduced in QEMU 2.10 to allow the guest
>> to be presented a new boot-time device tree after CAS negotiation.
>> CAS-generated resets rely on qemu_system_reset_requ
On 26/03/2020 16:40, David Gibson wrote:
> Currently, we can't properly handle unplug of NVLink2 devices, because we
> don't have code to tear down their special memory resources. There's not
> a lot of impetus to implement that. Since hardware NVLink2 devices can't
> be hot unplugged, the gues
78b145a0330b9c44478f7404b97a710e692bfc96:
pseries: Update SLOF firmware image (2020-03-27 13:58:00 +1100)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 965008 -> 965112 bytes
r
e sizes and even if they did not, the resulting page
size would be 0x8000... (gcc 9.2) and
ioctl(VFIO_IOMMU_SPAPR_TCE_CREATE) would fail anyway.
Signed-off-by: Alexey Kardashevskiy
---
hw/vfio/spapr.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/vfio/s
On 23/03/2020 21:55, Peter Maydell wrote:
> On Tue, 21 Aug 2018 at 05:33, David Gibson
> wrote:
>>
>> From: Alexey Kardashevskiy
>>
>> At the moment the PPC64/pseries guest only supports 4K/64K/16M IOMMU
>> pages and POWER8 CPU supports the exact same
On 18/03/2020 09:33, David Gibson wrote:
> On Tue, Mar 17, 2020 at 11:30:31AM +0100, Paolo Bonzini wrote:
>> On 17/03/20 11:03, David Gibson wrote:
>>> pseries: Update SLOF firmware image
>>> ppc/spapr: Move GPRs setup to one place
>>> pseries: Update SLOF firmware image
>>>
b7cf539920376542f03df8337602c3b8974bd1a1:
pseries: Update SLOF firmware image (2020-03-17 10:27:34 +1100)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 968848 -> 965008 bytes
r
problem is that SLOF copies the number of bytes it
reserved (2KB for now) so QEMU needs to reserve at least this much;
SLOF will be fixed separately to check that rtas-size from QEMU is
enough for those 20 bytes the H_RTAS hcall.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr.h | 1
re quite ready to merge
>> it yet. With this applied, I get zero output on a virtio-serial based
>> console:
>>
>> ie.
>> -chardev stdio,id=con0 -device virtio-serial -device
>> virtconsole,chardev=con0
>>
>> FYI, virtio-serial is a bit broken for
8b1987b232d0da2df1f33bf9e3e25fcb1874b91d:
pseries: Update SLOF firmware image (2020-03-12 15:04:40 +1100)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 968616 -> 968848 by
On 11/03/2020 20:43, Paolo Bonzini wrote:
> On 10/03/20 06:07, Alexey Kardashevskiy wrote:
>> The PAPR platform which describes an OS environment that's presented by
>> a combination of a hypervisor and firmware. The features it specifies
>> require collaboration be
ith:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=df5be5be8735
Signed-off-by: Alexey Kardashevskiy
---
The example command line is:
pbuild/qemu-killslof-localhost-ppc64/ppc64-softmmu/qemu-system-ppc64 \
-nodefaults \
-chardev stdio,id=STDIO0,signal=off,mux=on
leaves
writing FDT to the guest in the H_CAS handler.
This should not cause any behavioral change.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr.h | 7 +
hw/ppc/spapr.c | 1 -
hw/ppc/spapr_hcall.c | 67 ++
3 files chan
ed to the guest".
Please comment. Thanks.
Alexey Kardashevskiy (3):
ppc/spapr: Move GPRs setup to one place
spapr/cas: Separate CAS handling from rebuilding the FDT
spapr: Implement Open Firmware client interface
hw/ppc/Makefile.objs|1 +
pc-bios/vof/Makefile
mlinux can find this from the device tree but zImage from
distro kernels cannot).
This extends spapr_cpu_set_entry_state() to take more registers. This
should cause no behavioral change.
Signed-off-by: Alexey Kardashevskiy
---
Changes:
v7:
* removed r5 as it points to prom entry which is now pro
On 27/02/2020 17:35, Paolo Bonzini wrote:
> On 27/02/20 00:38, Alexey Kardashevskiy wrote:
>>
>>
>> On 26/02/2020 22:34, Paolo Bonzini wrote:
>>> On 26/02/20 00:58, Alexey Kardashevskiy wrote:
>>>>
>>>>
>>>> On 21/02/2020 19:27,
On 26/02/2020 22:34, Paolo Bonzini wrote:
> On 26/02/20 00:58, Alexey Kardashevskiy wrote:
>>
>>
>> On 21/02/2020 19:27, Paolo Bonzini wrote:
>>> On 21/02/20 01:18, Alexey Kardashevskiy wrote:
>>>> I am not quite sure I understood the request. Write m
On 21/02/2020 19:27, Paolo Bonzini wrote:
> On 21/02/20 01:18, Alexey Kardashevskiy wrote:
>> I am not quite sure I understood the request. Write my own small
>> firmware and replace GRUB with it? The firmware from 5/5 reads first 2
>> sectors and the entire PReP, I cou
On 18/02/2020 16:48, Philippe Mathieu-Daudé wrote:
> On 2/17/20 11:46 PM, David Gibson wrote:
>> On Mon, Feb 17, 2020 at 11:24:11AM +0100, Philippe Mathieu-Daudé wrote:
>>> On 2/17/20 10:26 AM, Philippe Mathieu-Daudé wrote:
>>>> Hi Alexey,
>>>>
>
into
slof from ext4 - there are still problems) and it broke things elsewhere.
On 21/02/2020 14:52, Alexey Kardashevskiy wrote:
> The following changes since commit 438bafcac55308eef4f9029c94dbadd2c7ac3bb7:
>
> hw/ppc/virtex_ml507:fix leak of fdevice tree blob (2020-02-21 09:15:04
fcd350cb4646255845f643cdb1711bb7004038e7:
pseries: Update SLOF firmware image (2020-02-21 14:20:23 +1100)
Alexey Kardashevskiy (1):
pseries: Update SLOF firmware image
pc-bios/README | 2 +-
pc-bios/slof.bin | Bin 931032 -> 968
On 20/02/2020 21:01, Paolo Bonzini wrote:
> On 20/02/20 07:16, Alexey Kardashevskiy wrote:
>> This is another attempt to implement minimalistic
>> Open Firmware Client Interface in QEMU.
>>
>> With this thing, I can boot unmodified Ubuntu 18.04 and Fedora 30
>&g
VIO_SPAPR_VTY_DEVICE. The OF client is going to need this.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr_vio.h | 1 +
hw/char/spapr_vty.c| 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/hw/ppc/spapr_vio.h b/include/hw/ppc/spapr_vio.h
index bed7df60e35c
leaves
writing FDT to the guest in the H_CAS handler.
This should not cause any behavioral change.
Signed-off-by: Alexey Kardashevskiy
---
include/hw/ppc/spapr.h | 7 +
hw/ppc/spapr.c | 1 -
hw/ppc/spapr_hcall.c | 67 ++
3 files chan
sed memory is:
0..4000 - the initial firmware
1..18 - stack
This OF CI does not implement "interpret".
With this basic support, this can only boot into kernel directly.
However this is just enough for the petitboot kernel and initradmdisk to
boot from any possible source.
Signe
-2dd88cbc6...@ozlabs.ru/
5/5 is kind of controvertial though. This respin does not include
networking.
This is based on sha1
015fb0ead60d Chen Qun "hw/ppc/virtex_ml507:fix leak of fdevice tree blob".
Please comment. Thanks.
Alexey Kardashevskiy (5):
ppc/spapr: Move GPRs setup to one pla
101 - 200 of 3705 matches
Mail list logo
