Hi Eric,
> On 19 Jun 2025, at 13:29, Eric Auger wrote:
>
> Hi,
>
> On 6/17/25 5:50 PM, Miguel Luis wrote:
>> Hi Eric,
>>
>>> On 17 Jun 2025, at 15:41, Eric Auger wrote:
>>>
>>>
>>>
>>> On 6/17/25 5:23 PM, Miguel Luis
De: Eric Auger
Enviado: quinta-feira, junho 19, 2025 8:19:47 da manhã
Para: Marc Zyngier
Cc: eric.auger@gmail.com ; qemu-devel@nongnu.org
; qemu-...@nongnu.org ; Miguel Luis
; peter.mayd...@linaro.org ;
richard.hender...@linaro.org ;
gkulka
Hi Eric,
> On 17 Jun 2025, at 15:41, Eric Auger wrote:
>
>
>
> On 6/17/25 5:23 PM, Miguel Luis wrote:
>> Hi Alyssa,
>>
>>> On 17 Jun 2025, at 14:17, Alyssa Ross wrote:
>>>
>>> Eric Auger writes:
>>>
>>>> From: H
so check only in-kernel GICv3 is used along with KVM EL2.
>>
>> Signed-off-by: Haibo Xu
>> Signed-off-by: Miguel Luis
>> Signed-off-by: Eric Auger
>> Reviewed-by: Richard Henderson
>
> Hi! From what I can tell, this will produce an error on hosts that
> d
Hi Alex,
> On 11 Jun 2025, at 14:31, Alex Bennée wrote:
>
> Miguel Luis writes:
>
>> Hi Philippe,
>>
>>> On 6 Jun 2025, at 16:44, Philippe Mathieu-Daudé wrote:
>>>
>>> Signed-off-by: Philippe Mathieu-Daudé
>>> ---
>>>
Hi Philippe,
> On 6 Jun 2025, at 16:44, Philippe Mathieu-Daudé wrote:
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> hw/arm/virt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index 9a6cd085a37..d55ce2c0f4e 100644
> --- a/hw/arm/vir
> On 27 May 2025, at 16:52, Marc Zyngier wrote:
>
> On Tue, 27 May 2025 16:55:32 +0100,
> Miguel Luis wrote:
>>
>> Hi Marc,
>>
>>> On 27 May 2025, at 13:46, Marc Zyngier wrote:
>>>
>>> On Tue, 27 May 2025 14:24:31 +0100,
>>&
Hi Marc,
> On 27 May 2025, at 13:46, Marc Zyngier wrote:
>
> On Tue, 27 May 2025 14:24:31 +0100,
> Miguel Luis wrote:
>>
>>
>>
>>> On 27 May 2025, at 12:02, Marc Zyngier wrote:
>>>
>>> On Tue, 27 May 2025 12:40:35 +0100,
>>
> On 27 May 2025, at 12:02, Marc Zyngier wrote:
>
> On Tue, 27 May 2025 12:40:35 +0100,
> Miguel Luis wrote:
>>
>> Hi Marc,
>>
>>> On 27 May 2025, at 07:39, Marc Zyngier wrote:
>>>
>>> Hi Eric,
>>>
>>> On Tue,
> On 27 May 2025, at 12:01, Marc Zyngier wrote:
>
> On Tue, 27 May 2025 12:33:23 +0100,
> Miguel Luis wrote:
>>
>> Hi Eric,
>>
>>> On 27 May 2025, at 06:24, Eric Auger wrote:
>>>
>>> Now that ARM nested virt has landed in kvm/next,
Hi Marc,
> On 27 May 2025, at 07:39, Marc Zyngier wrote:
>
> Hi Eric,
>
> On Tue, 27 May 2025 07:24:32 +0100,
> Eric Auger wrote:
>>
>> Now that ARM nested virt has landed in kvm/next, let's turn the series
>> into a PATCH series. The linux header update was made against kvm/next.
>>
>> For
Hi Eric,
> On 27 May 2025, at 06:24, Eric Auger wrote:
>
> Now that ARM nested virt has landed in kvm/next, let's turn the series
> into a PATCH series. The linux header update was made against kvm/next.
>
> For gaining virt functionality in KVM accelerated L1, The host needs to
> be booted wit
pected which concerns this
> patch-set. Please have a look.
>
For arm64:
I’ve ran make check and bios-tables-test passed successfully and got 0 failed
tests.
After boot the number of vcpus matched what was initially requested via -smp
cpus.
I’ve also tested this patchset alongside the upco
Hi Gustavo,
> On 18 Oct 2024, at 17:57, Gustavo Romero wrote:
>
> Hi Miguel,
>
> On 10/15/24 15:41, Miguel Luis wrote:
>> Hi Salil,
>> I’ve ran the usual tests successfully of hotplug/unplug from the number of
>> cold-booted cpus up to maxcpus and migratio
8]
> https://lore.kernel.org/lkml/20210608154805.216869-1-jean-phili...@linaro.org/
> [19] https://lore.kernel.org/all/20230913163823.7880-1-james.mo...@arm.com/
> [20]
> https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html#gicc-cpu-interface-flags
> [21]
&
Hi Salil,
I’ve ran the usual tests successfully of hotplug/unplug from the number of
cold-booted cpus up to maxcpus and migration on ARM. Please feel free to add:
Tested-by: Miguel Luis
Thanks
Miguel
> On 14 Oct 2024, at 19:22, Salil Mehta wrote:
>
> Certain CPU architecture speci
Hi Salil,
> On 9 Oct 2024, at 03:17, Salil Mehta wrote:
>
> This patch adds various utility functions that may be required to fetch or
> check
> the state of possible vCPUs. It also introduces the concept of *disabled*
> vCPUs,
> which are part of the *possible* vCPUs but are not enabled. This
cket_id, 0),
> +DEFINE_PROP_INT32("cluster-id", ARMCPU, cluster_id, 0),
> +DEFINE_PROP_INT32("core-id", ARMCPU, core_id, 0),
> +DEFINE_PROP_INT32("thread-id", ARMCPU, thread_id, 0),
> DEFINE_PROP_INT32("core-count", ARMCPU, cor
Hi Peter,
> On 8 Oct 2024, at 11:53, Peter Maydell wrote:
>
> On Fri, 27 Sept 2024 at 19:40, Annie Li wrote:
>>
>> From: Miguel Luis
>>
>> For reference: qmp_system_sleep relies on wakeup support delegated
>> by qemu_wakeup_suspe
cpus.
Hot unplug down to the number of boot cpus.
Hotplug vcpus then migrate to a new VM.
Hot unplug down to the number of boot cpus then migrate to a new VM.
Up to 6 successive live migrations.
And in which LGTM.
Please feel free to add,
Tested-by: Miguel Luis
Regards,
Miguel
[1]
https:/
Hi Eric,
> On 8 Feb 2024, at 15:55, Eric Auger wrote:
>
> Hi Miguel,
>
> On 2/27/23 17:37, Miguel Luis wrote:
>> This series adds ARMv8.3/8.4 nested virtualization support in KVM mode.
>>
>> To enable nested virtualization for a guest, the host must expose EL2
, which is a good
> idea anyway and also works around what Marc Z and I think is
> a KVM bug that otherwise causes boot of the L2 kernel to hang
> * patch 3 is a GIC bug which is not FEAT_NV specific but for
> some reason only manifests when booting an L1 kernel under NV
>
I&#
> On 6 Dec 2023, at 14:25, Michal Suchánek wrote:
>
> On Wed, Dec 06, 2023 at 01:17:08PM -0100, Miguel Luis wrote:
>> Hi!
>>
>> On 04/12/2023 18:40, Philippe Mathieu-Daudé wrote:
>>> Unplugging vCPU triggers the following assertion in
>>
Hi!
On 04/12/2023 18:40, Philippe Mathieu-Daudé wrote:
> Unplugging vCPU triggers the following assertion in
> tcg_register_thread():
>
> 796 void tcg_register_thread(void)
> 797 {
> ...
> 812 /* Claim an entry in tcg_ctxs */
> 813 n = qatomic_fetch_inc(&tcg_cur_ctxs);
> 814 g_as
> On 16 Oct 2023, at 10:01, Miguel Luis wrote:
>
> Hi Salil,
>
>> On 16 Oct 2023, at 09:52, Salil Mehta wrote:
>>
>> Hi Miguel,
>>
>>> From: Miguel Luis
>>> Sent: Friday, October 13, 2023 5:34 PM
>>> To: Salil Mehta
&
Hi Salil,
> On 16 Oct 2023, at 09:52, Salil Mehta wrote:
>
> Hi Miguel,
>
>> From: Miguel Luis
>> Sent: Friday, October 13, 2023 5:34 PM
>> To: Salil Mehta
>> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org; Marc Zyngier
>> ; jean-phili...
++
> include/exec/gdbstub.h | 5 ++
> include/hw/acpi/cpu.h | 5 +-
> include/hw/acpi/cpu_hotplug.h | 4 ++
> include/hw/acpi/generic_event_device.h | 5 ++
> include/hw/core/cpu.h | 1 +
> include/sysemu/kvm.h | 16 +++
> system/physmem.c | 29
> 15 files changed, 184 insertions(+), 27 deletions(-)
>
I tested it for Arm64, make check, boot/reboot, live migration and found no
issues,
so for this, please feel free to add:
Tested-by: Miguel Luis
Thank you,
Miguel
> --
> 2.34.1
>
Hi Salil,
> On 12 Oct 2023, at 17:54, Salil Mehta wrote:
>
> Hi Miguel,
>
>> From: Miguel Luis
>> Sent: Thursday, October 12, 2023 6:02 PM
>> To: Salil Mehta
>> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org; Marc Zyngier
>> ; jean-phili...
> https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html#gic-cpu-interface-gicc-structure
> [8] https://bugzilla.tianocore.org/show_bug.cgi?id=4481#c5
> [9]
> https://cloud.google.com/kubernetes-engine/docs/concepts/verticalpodautoscaler
> [10]
> https://doc
Hi Eric,
Thanks in advance for your comment.
> On 6 Jul 2023, at 08:16, Eric Auger wrote:
>
> Hi Miguel,
>
> On 2/27/23 17:37, Miguel Luis wrote:
>> From: Haibo Xu
>>
>> KVM_CAP_ARM_EL2 must be supported by the cpu to enable ARM_FEATURE_EL2.
>> EL2 b
Hi Marc,
> On 6 Mar 2023, at 13:32, Marc Zyngier wrote:
>
> On Mon, 06 Mar 2023 14:02:33 +,
> Peter Maydell wrote:
>>
>> On Mon, 27 Feb 2023 at 16:37, Miguel Luis wrote:
>>>
>>> From: Haibo Xu
>>>
>>> Use the
Hi Peter,
> On 6 Mar 2023, at 13:02, Peter Maydell wrote:
>
> On Mon, 27 Feb 2023 at 16:37, Miguel Luis wrote:
>>
>> From: Haibo Xu
>>
>> Use the VGIC maintenance IRQ if VHE is requested. As per the ARM GIC
>> Architecture Specification for GICv3
Hi Richard,
> On 27 Feb 2023, at 18:26, Richard Henderson
> wrote:
>
> On 2/27/23 06:37, Miguel Luis wrote:
>> -if (vms->virt && (kvm_enabled() || hvf_enabled())) {
>> +if (vms->virt && (kvm_enabled() || hvf_enabled())
>> +&am
Hi Richard,
> On 27 Feb 2023, at 18:24, Richard Henderson
> wrote:
>
> On 2/27/23 06:37, Miguel Luis wrote:
>> From: Haibo Xu
>> KVM_CAP_ARM_EL2 must be supported by the cpu to enable ARM_FEATURE_EL2.
>> EL2 bits on ID_AA64PFR0 state unsupported on the v
Hi Cornelia,
> On 27 Feb 2023, at 15:49, Cornelia Huck wrote:
>
> On Mon, Feb 27 2023, Miguel Luis wrote:
>
>> From: Haibo Xu
>>
>> linux-headers define host properties needed for the VMM to interact with
>> KVM, so let's include them *while* they&
From: Haibo Xu
Introduce query support for KVM_CAP_ARM_EL2.
Ref:
https://lore.kernel.org/qemu-devel/65b8771bfecada08bf02c9cf87c2f0f9cdf943b3.1617281290.git.haibo...@linaro.org/
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
---
target/arm/kvm64.c | 5 +
target/arm/kvm_arm.h | 12
From: Haibo Xu
VHE enablement if host supports EL2.
Ref:
https://lore.kernel.org/qemu-devel/b7c2626e6c720ccc43e57197dff3dac72d613640.1616052890.git.haibo...@linaro.org/
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
---
hw/arm/virt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion
.2880505-1-...@kernel.org/
Miguel Luis (5):
linux-headers: [kvm,arm64] add the necessary definitions to match host
kernel
hw/intc/gicv3: add support for setting KVM vGIC maintenance IRQ
target/arm/kvm: add helper to detect EL2 when using KVM
target/arm: enable feature ARM_FEATURE_EL2
://lore.kernel.org/qemu-devel/49a4944e2f148c56938380b981afe154b7a8b7ee.1617281290.git.haibo...@linaro.org/
Signed-off-by: Haibo Xu
[Miguel Luis: avoid direct usage of helpers (_check_attr(); _access())]
Signed-off-by: Miguel Luis
---
hw/arm/virt.c | 5 +
hw/intc
qemu-devel/636b5932e4cf061b6f97516e82d4319c1d29b871.1616052889.git.haibo...@linaro.org/
Signed-off-by: Haibo Xu
Signed-off-by: Miguel Luis
---
linux-headers/asm-arm64/kvm.h | 2 ++
linux-headers/linux/kvm.h | 1 +
2 files changed, 3 insertions(+)
diff --git a/linux-headers/asm-arm64/kvm.h b/linux-headers/asm-a
[Miguel Luis: use of ID_AA64PFR0 for cpu features]
Signed-off-by: Miguel Luis
---
target/arm/cpu.h | 2 +-
target/arm/kvm64.c | 16
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/target/arm/cpu.h b/target/arm/cpu.h
index 9aeed3c848..de2a88b43e 100644
--- a/target
//
00F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 //
-0100: 00 00 00 00 00 00 00 00 00 00 00 00 //
+0100: 00 00 00 00 00 00 00 00 00 00 00 00 51 45 4D 55 // QEMU
+0110: 00 00 00 00
MADT has been updated with the GIC Structures from ACPI 6.0 Errata A
and so MADT revision and GICC Structure must be updated also.
Fixes: 37f33084ed2e ("acpi: arm/virt: madt: use build_append_int_noprefix() API
to compose MADT table")
Signed-off-by: Miguel Luis
Reviewed-by: Ani Sinh
i.org/sites/default/files/resources/ACPI_6_0_Errata_A.PDF
This patch series originates from a previous RFC [1] discussion. Reviewed-by
tags were kept on patches 2/4 and 3/4.
[1]: https://lists.gnu.org/archive/html/qemu-devel/2022-10/msg01326.html
Miguel Luis (4):
tests/acpi: virt: allow acpi MAD
ed through a
supplemental vendor-specific hypervisor API. Firmware implementers would
place zero bytes into this field, denoting that no hypervisor is present in
the actual firmware."
Signed-off-by: Miguel Luis
Reviewed-by: Ani Sinha
---
hw/acpi/aml-build.c | 13 ++---
Step 3 from bios-tables-test.c documented procedure.
Signed-off-by: Miguel Luis
---
tests/qtest/bios-tables-test-allowed-diff.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8b
> On 11 Oct 2022, at 05:02, Ani Sinha wrote:
>
> On Mon, Oct 10, 2022 at 6:53 PM Miguel Luis wrote:
>>
>> Update the Fixed ACPI Description Table (FADT) to revision 6.0 of the ACPI
>> specification adding the field "Hypervisor Vendor Identity" that was mis
sion follows Ani Sinha's suggestion [2] of using "QEMU" for the
hypervisor vendor ID.
[1]: https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg00911.html
[2]: https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg00989.html
Signed-off-by: Miguel Luis
---
hw/acpi/aml
//
00F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 //
-0100: 00 00 00 00 00 00 00 00 00 00 00 00 //
+0100: 00 00 00 00 00 00 00 00 00 00 00 00 51 45 4D 55 // QEMU
+0110: 00 00 00 00
ery welcome.
Thanks in advance.
Miguel
[1]: https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg00989.html
Miguel Luis (4):
tests/acpi: virt: allow acpi MADT and FADT changes
acpi: fadt: support revision 6.0 of the ACPI specification
acpi:
MADT has been updated with the GIC Structures from ACPI 6.0 Errata A
and so MADT revision and GICC Structure must be updated also.
Fixes: 37f33084ed2e ("acpi: arm/virt: madt: use build_append_int_noprefix() API
to compose MADT table")
Signed-off-by: Miguel Luis
Reviewed-by: Ani Sinh
Step 3 from bios-tables-test.c documented procedure.
Signed-off-by: Miguel Luis
---
tests/qtest/bios-tables-test-allowed-diff.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8b
> On 7 Oct 2022, at 15:21, Ani Sinha wrote:
>
> On Fri, Oct 7, 2022 at 8:16 PM Miguel Luis wrote:
>>
>> The ACPI GTDT table contains two invalid 64-bit physical addresses according
>> to
>> the ACPI spec. 6.5 [1]. Those are the Counter Control Base physic
00 00 00 00 00 00 00 1A 00 00 00 00 00 00 00 //
-0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 //
+0050: FF FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 //
Signed-off-by: Miguel Luis
Acked-by: Ani Sinha
---
tests/data/acpi/virt
Step 3 from bios-tables-test.c documented procedure.
Signed-off-by: Miguel Luis
Acked-by: Ani Sinha
---
tests/qtest/bios-tables-test-allowed-diff.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
0x0.
[1]:
https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html#gtdt-table-structure
Changelog:
v2:
Updated with collected tags from v1.
v1: https://lists.nongnu.org/archive/html/qemu-devel/2022-09/msg02847.html
Miguel Luis (3):
tests/acpi: virt: allow acpi GTDT changes
begin()/acpi_table_end() instead of build_header()")
Signed-off-by: Miguel Luis
Reviewed-by: Ani Sinha
---
hw/arm/virt-acpi-build.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index 9b3aee01bf..13c6e3e468 100644
--
> On 21 Sep 2022, at 03:39, Ani Sinha wrote:
>
>
>
> On Tue, 20 Sep 2022, Miguel Luis wrote:
>
>> Step 6 & 7 of the bios-tables-test.c documented procedure.
>>
>> Differences between disassembled ASL files for GTDT:
>>
&
Hi Ani,
> On 7 Oct 2022, at 04:25, Ani Sinha wrote:
>
>
>
> On Thu, 6 Oct 2022, Miguel Luis wrote:
>
>> Update the Fixed ACPI Description Table (FADT) to revision 6.0 of the ACPI
>> specification adding the field "Hypervisor Vendor Identity" that was
0 00 00 00 00 //
-0100: 00 00 00 00 00 00 00 00 00 00 00 00 //
+0100: 00 00 00 00 00 00 00 00 00 00 00 00 74 63 67 00 // tcg.
+0110: 00 00 00 00 //
Signed-off-by: Miguel Luis
---
tests/
MADT has been updated with the GIC Structures from ACPI 6.0 Errata A
and so MADT revision and GICC Structure must be updated also.
Fixes: 37f33084ed2e ("acpi: arm/virt: madt: use build_append_int_noprefix() API
to compose MADT table")
Signed-off-by: Miguel Luis
---
hw/arm/virt-ac
leration name. This would
provide values like 'KVM' for example when KVM is used.
Ref: https://uefi.org/sites/default/files/resources/ACPI_6_0_Errata_A.PDF
Open to discussion, your comments, thoughts and suggestions are very welcome.
Thanks in advance.
Miguel
Miguel Luis (4):
tests/a
provide that information?
On this RFC there's the suggestion of having this information in sync by the
current acceleration name. This also seems to imply that QEMU, which generates
the FADT table, and the FADT consumer need to be in sync with the values of this
field.
Signed-off-by: Mi
Step 3 from bios-tables-test.c documented procedure.
Signed-off-by: Miguel Luis
---
tests/qtest/bios-tables-test-allowed-diff.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8b
Step 3 from bios-tables-test.c documented procedure.
Signed-off-by: Miguel Luis
---
tests/qtest/bios-tables-test-allowed-diff.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/qtest/bios-tables-test-allowed-diff.h
b/tests/qtest/bios-tables-test-allowed-diff.h
index dfb8523c8b
00 00 00 00 00 00 00 1A 00 00 00 00 00 00 00 //
-0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 //
+0050: FF FF FF FF FF FF FF FF 00 00 00 00 00 00 00 00 //
Signed-off-by: Miguel Luis
---
tests/data/acpi/virt/GTDT
begin()/acpi_table_end() instead of build_header()")
Signed-off-by: Miguel Luis
---
hw/arm/virt-acpi-build.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index 9b3aee01bf..13c6e3e468 100644
--- a/hw/arm/virt-acpi-bui
0x0.
[1]:
https://uefi.org/specs/ACPI/6.5/05_ACPI_Software_Programming_Model.html#gtdt-table-structure
Miguel Luis (3):
tests/acpi: virt: allow acpi GTDT changes
acpi: arm/virt: build_gtdt: fix invalid 64-bit physical addresses
tests/acpi: virt: update ACPI GTDT binaries
hw/arm/virt-acpi
68 matches
Mail list logo
