When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
I don't understand the issue here. the vgic_irq->group field does not exist in 4.16 (neither in the first nor the last version). Nor does the line you are modifying.
Both exist in mainline, but what you are mentioning shouldn't be an issue in mainline since vgic_irq->group gets initialized in kvm_vgic_vcpu_init for SGIs and PPIs (i.e. intid < 32) which includes your interrupt.
Cheers,
quoted hunk
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
I don't understand the issue here. the vgic_irq->group field does not
exist in 4.16 (neither in the first nor the last version). Nor does the
line you are modifying.
Guest's kernel version is 4.16 and Host's kernel version is mainline.
vgic_irq is a structure of Host's kvm.
Both exist in mainline, but what you are mentioning shouldn't be an
issue in mainline since vgic_irq->group gets initialized in
kvm_vgic_vcpu_init for SGIs and PPIs (i.e. intid < 32) which includes
your interrupt.
Initialization sequence of several components is like this;
1. kvm_vgic_vcpu_init ---- here, dist is not initialized at this time.
and the value of irq->group depends on
dist->vgic_model. but now dist->vgic_model = 0
and irq->group=0.
2. vgic_create ----- assign to dist->vgic_model.
3. kvm_vgic_dist_init
thanks.
Cheers,
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
I don't understand the issue here. the vgic_irq->group field does not
exist in 4.16 (neither in the first nor the last version). Nor does the
line you are modifying.
Guest's kernel version is 4.16 and Host's kernel version is mainline.
vgic_irq is a structure of Host's kvm.
quoted
Both exist in mainline, but what you are mentioning shouldn't be an
issue in mainline since vgic_irq->group gets initialized in
kvm_vgic_vcpu_init for SGIs and PPIs (i.e. intid < 32) which includes
your interrupt.
Initialization sequence of several components is like this;
1. kvm_vgic_vcpu_init ---- here, dist is not initialized at this time.
and the value of irq->group depends on
dist->vgic_model. but now dist->vgic_model = 0
and irq->group=0.
2. vgic_create ----- assign to dist->vgic_model.
3. kvm_vgic_dist_init
I see, thanks for explaining.
This means the initialization in kvm_vgic_vcpu_init depends on whether userland creates the GIC device first or the vcpus first...
I don't think the issue lies in vgic_v3_populate_lr, but in kvm_vgic_vcpu_init which clearly expects dist->vgic_model to be initialized in two places. However, the comment at the top of vgic-init.c states:
* CPU Interface:
*
* - kvm_vgic_vcpu_init(): initialization of static data that
* doesn't depend on any sizing information or emulation type. No
* allocation is allowed there.
So I don't think we're supposed to check for dist->vgic_model here. Those two checks should probably be moved elsewhere (maybe in kvm_vgic_vcpu_enable?) once the gic type has been set.
Thanks,
thanks.
quoted
Cheers,
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Andre Przywara <andre.przywara@arm.com> Date: 2018-11-15 14:39:14
On Thu, 15 Nov 2018 23:14:08 +0800
Peng Hao [off-list ref] wrote:
Hi,
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
quoted hunk
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Cheers,
Andre.
val |= ICH_LR_GROUP;
val |= (u64)irq->priority << ICH_LR_PRIORITY_SHIFT;
From: Marc Zyngier <hidden> Date: 2018-11-15 15:06:23
On Thu, 15 Nov 2018 15:14:08 +0000,
Peng Hao [off-list ref] wrote:
quoted hunk
When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This patch makes exactly zero sense. The group is a property of the
interrupt, and has nothing to do with the model used for the emulation
Which version of the kernel is this against? What userspace are you
using? How can I reproduce this issue?
Thanks,
M.
--
Jazz is not dead, it just smell funny.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Cheers,
Andre.
quoted
val |= ICH_LR_GROUP;
val |= (u64)irq->priority << ICH_LR_PRIORITY_SHIFT;
When virtual machine starts, hang up. The kernel version of guest
is 4.16. Host support vgic_v3.
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0? That sounds wrong, Linux should configure all it's interrupts as non-secure group1.
--
Julien Thierry
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
From: Mark Rutland <mark.rutland@arm.com> Date: 2018-11-19 09:10:31
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
Thanks,
Mark.
From: Marc Zyngier <hidden> Date: 2018-11-19 09:26:15
On 19/11/2018 09:10, Mark Rutland wrote:
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I doubt it. The EDK2 bug resulted in no interrupt being delivered due to
the group being set to 1, and the interrupt being acknowledged through
the Group0 accessor. Also, this was a 32bit special, and 64bit EDK2 was
just fine.
What Peng describes here is the guest writing the group as 0, which
doesn't make much sense (I certainly don't see EDK2 doing that).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
From: Marc Zyngier <hidden> Date: 2018-11-19 12:49:40
On 19/11/2018 09:10, Mark Rutland wrote:
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I will update the UEFI version in recent days and test it later.
Thanks.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
Thanks.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
From: Christoffer Dall <hidden> Date: 2018-11-21 11:06:36
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)irq->config=VGIC_CONFIG_LEVEL;}-/*-*GICv3canonlybecreatedviatheKVM_DEVICE_CREATEAPIand-*sowealwaysknowtheemulationtypeatthispointasit's-*eitherexplicitlyconfiguredasGICv3,orexplicitly-*configuredasGICv2,ornotconfiguredyetwhichalso-*impliesGICv2.-*/if(dist->vgic_model==KVM_DEV_TYPE_ARM_VGIC_V3)irq->group=1;else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)if(ret)gotoout;+/* Initialize groups on CPUs created before the VGIC type was known */+kvm_for_each_vcpu(i,vcpu,kvm){+structvgic_cpu*vgic_cpu=&vcpu->arch.vgic_cpu;++for(i=0;i<VGIC_NR_PRIVATE_IRQS;i++){+structvgic_irq*irq=&vgic_cpu->private_irqs[i];+irq->group=1;+}+}+if(vgic_has_its(kvm)){ret=vgic_v4_init(kvm);if(ret)
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)irq->config=VGIC_CONFIG_LEVEL;}-/*-*GICv3canonlybecreatedviatheKVM_DEVICE_CREATEAPIand-*sowealwaysknowtheemulationtypeatthispointasit's-*eitherexplicitlyconfiguredasGICv3,orexplicitly-*configuredasGICv2,ornotconfiguredyetwhichalso-*impliesGICv2.-*/if(dist->vgic_model==KVM_DEV_TYPE_ARM_VGIC_V3)irq->group=1;else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)if(ret)gotoout;+/* Initialize groups on CPUs created before the VGIC type was known */+kvm_for_each_vcpu(i,vcpu,kvm){+structvgic_cpu*vgic_cpu=&vcpu->arch.vgic_cpu;++for(i=0;i<VGIC_NR_PRIVATE_IRQS;i++){+structvgic_irq*irq=&vgic_cpu->private_irqs[i];+irq->group=1;+}+}+if(vgic_has_its(kvm)){ret=vgic_v4_init(kvm);if(ret)
If the value of dist->vgic_model is not properly initialized at the time we call kvm_vgic_vcpu_init is call, won't we still overwrite the irq->group when we get there? (I still haven't seen why we could consider dist->vgic_model is initialized at that point).
Shouldn't we do the irq->group initialization somewhere in kvm_arch_vcpu_ioctl_vcpu_init? (with some vgic_* function to encapsulate it of course). At that point I believe we know that dist->vgic_model is initialized.
Cheers,
--
Julien Thierry
From: Christoffer Dall <hidden> Date: 2018-11-21 15:24:14
On Wed, Nov 21, 2018 at 12:17:45PM +0000, Julien Thierry wrote:
On 21/11/18 11:06, Christoffer Dall wrote:
quoted
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)irq->config=VGIC_CONFIG_LEVEL;}-/*-*GICv3canonlybecreatedviatheKVM_DEVICE_CREATEAPIand-*sowealwaysknowtheemulationtypeatthispointasit's-*eitherexplicitlyconfiguredasGICv3,orexplicitly-*configuredasGICv2,ornotconfiguredyetwhichalso-*impliesGICv2.-*/if(dist->vgic_model==KVM_DEV_TYPE_ARM_VGIC_V3)irq->group=1;else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)if(ret)gotoout;+/* Initialize groups on CPUs created before the VGIC type was known */+kvm_for_each_vcpu(i,vcpu,kvm){+structvgic_cpu*vgic_cpu=&vcpu->arch.vgic_cpu;++for(i=0;i<VGIC_NR_PRIVATE_IRQS;i++){+structvgic_irq*irq=&vgic_cpu->private_irqs[i];+irq->group=1;+}+}+if(vgic_has_its(kvm)){ret=vgic_v4_init(kvm);if(ret)
If the value of dist->vgic_model is not properly initialized at the time we
call kvm_vgic_vcpu_init is call, won't we still overwrite the irq->group
when we get there?
I don't understand this question. When we get where?
(I still haven't seen why we could consider
dist->vgic_model is initialized at that point).
Because there is no enforced ordering between creating VCPUs and
creating the VGIC.
Shouldn't we do the irq->group initialization somewhere in
kvm_arch_vcpu_ioctl_vcpu_init? (with some vgic_* function to encapsulate it
of course). At that point I believe we know that dist->vgic_model is
initialized.
See above. AFAICT we don't have a single point at which we can do
everything because creation of the two components can be interleaved.
We could hook into kvm_vcpu_first_run_init(), but then userspace can
observe uninitialized values if it looks at the GIC state prior to
running the VCPUs, which is also not great.
In other words, I think the problem is that you can do:
create_vcpu(0);
create_vgic(v3);
create_vcpu(2);
Now you'll have vcpu0 have its private IRQs set to group 0, and you'll
have vcpu1 have its private IRQs set to group 1 (prior to my patch).
Am I missing something?
Thanks,
Christoffer
On Wed, Nov 21, 2018 at 12:17:45PM +0000, Julien Thierry wrote:
quoted
On 21/11/18 11:06, Christoffer Dall wrote:
quoted
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)irq->config=VGIC_CONFIG_LEVEL;}-/*-*GICv3canonlybecreatedviatheKVM_DEVICE_CREATEAPIand-*sowealwaysknowtheemulationtypeatthispointasit's-*eitherexplicitlyconfiguredasGICv3,orexplicitly-*configuredasGICv2,ornotconfiguredyetwhichalso-*impliesGICv2.-*/if(dist->vgic_model==KVM_DEV_TYPE_ARM_VGIC_V3)irq->group=1;else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)if(ret)gotoout;+/* Initialize groups on CPUs created before the VGIC type was known */+kvm_for_each_vcpu(i,vcpu,kvm){+structvgic_cpu*vgic_cpu=&vcpu->arch.vgic_cpu;++for(i=0;i<VGIC_NR_PRIVATE_IRQS;i++){+structvgic_irq*irq=&vgic_cpu->private_irqs[i];+irq->group=1;+}+}+if(vgic_has_its(kvm)){ret=vgic_v4_init(kvm);if(ret)
If the value of dist->vgic_model is not properly initialized at the time we
call kvm_vgic_vcpu_init is call, won't we still overwrite the irq->group
when we get there?
I don't understand this question. When we get where?
Sorry, I meant when we get to the irq->group initialization in kvm_vgic_vcpu_init.
quoted
(I still haven't seen why we could consider
dist->vgic_model is initialized at that point).
Because there is no enforced ordering between creating VCPUs and
creating the VGIC.
Hmmm, I think that's what I am saying, so we shouldn't look at the value of vgic_dist->vgic_model since it could be uninitialized (or 0).
quoted
Shouldn't we do the irq->group initialization somewhere in
kvm_arch_vcpu_ioctl_vcpu_init? (with some vgic_* function to encapsulate it
of course). At that point I believe we know that dist->vgic_model is
initialized.
See above. AFAICT we don't have a single point at which we can do
everything because creation of the two components can be interleaved.
We could hook into kvm_vcpu_first_run_init(), but then userspace can
observe uninitialized values if it looks at the GIC state prior to
running the VCPUs, which is also not great.
In other words, I think the problem is that you can do:
create_vcpu(0);
create_vgic(v3);
create_vcpu(2);
Now you'll have vcpu0 have its private IRQs set to group 0, and you'll
have vcpu1 have its private IRQs set to group 1 (prior to my patch).
Am I missing something?
No, I just got confused between create_vgic and vgic_init. So the place looks fine. Sorry for the confusion.
The fact that we still check dist->vgic_model in kvm_vgic_vcpu_init (twice actually), however seems dodgy to me since it might not have been initialized.
Thanks,
--
Julien Thierry
From: Christoffer Dall <hidden> Date: 2018-11-22 10:45:56
On Wed, Nov 21, 2018 at 03:53:03PM +0000, Julien Thierry wrote:
On 21/11/18 15:24, Christoffer Dall wrote:
quoted
On Wed, Nov 21, 2018 at 12:17:45PM +0000, Julien Thierry wrote:
quoted
On 21/11/18 11:06, Christoffer Dall wrote:
quoted
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)irq->config=VGIC_CONFIG_LEVEL;}-/*-*GICv3canonlybecreatedviatheKVM_DEVICE_CREATEAPIand-*sowealwaysknowtheemulationtypeatthispointasit's-*eitherexplicitlyconfiguredasGICv3,orexplicitly-*configuredasGICv2,ornotconfiguredyetwhichalso-*impliesGICv2.-*/if(dist->vgic_model==KVM_DEV_TYPE_ARM_VGIC_V3)irq->group=1;else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)if(ret)gotoout;+/* Initialize groups on CPUs created before the VGIC type was known */+kvm_for_each_vcpu(i,vcpu,kvm){+structvgic_cpu*vgic_cpu=&vcpu->arch.vgic_cpu;++for(i=0;i<VGIC_NR_PRIVATE_IRQS;i++){+structvgic_irq*irq=&vgic_cpu->private_irqs[i];+irq->group=1;+}+}+if(vgic_has_its(kvm)){ret=vgic_v4_init(kvm);if(ret)
If the value of dist->vgic_model is not properly initialized at the time we
call kvm_vgic_vcpu_init is call, won't we still overwrite the irq->group
when we get there?
I don't understand this question. When we get where?
Sorry, I meant when we get to the irq->group initialization in
kvm_vgic_vcpu_init.
quoted
quoted
(I still haven't seen why we could consider
dist->vgic_model is initialized at that point).
Because there is no enforced ordering between creating VCPUs and
creating the VGIC.
Hmmm, I think that's what I am saying, so we shouldn't look at the value of
vgic_dist->vgic_model since it could be uninitialized (or 0).
quoted
quoted
Shouldn't we do the irq->group initialization somewhere in
kvm_arch_vcpu_ioctl_vcpu_init? (with some vgic_* function to encapsulate it
of course). At that point I believe we know that dist->vgic_model is
initialized.
See above. AFAICT we don't have a single point at which we can do
everything because creation of the two components can be interleaved.
We could hook into kvm_vcpu_first_run_init(), but then userspace can
observe uninitialized values if it looks at the GIC state prior to
running the VCPUs, which is also not great.
In other words, I think the problem is that you can do:
create_vcpu(0);
create_vgic(v3);
create_vcpu(2);
Now you'll have vcpu0 have its private IRQs set to group 0, and you'll
have vcpu1 have its private IRQs set to group 1 (prior to my patch).
Am I missing something?
No, I just got confused between create_vgic and vgic_init. So the place
looks fine. Sorry for the confusion.
The fact that we still check dist->vgic_model in kvm_vgic_vcpu_init (twice
actually), however seems dodgy to me since it might not have been
initialized.
It might not, but it might also be. In which case you want to
initialize the CPU to the right values. So you have:
1. VCPUs created before the VGIC are initialized according to the model
version when the VGIC is created.
2. VCPUs created after the VGIC is initialized are initialized according
to the model as they are created.
The alternative is to have a sync-point after the two above, but I
haven't been able to find a good API-backwards way of doing that.
Thanks,
Christoffer
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through >vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg >timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)
irq->config = VGIC_CONFIG_LEVEL;
}
- /*
- * GICv3 can only be created via the KVM_DEVICE_CREATE API and
- * so we always know the emulation type at this point as it's
- * either explicitly configured as GICv3, or explicitly
- * configured as GICv2, or not configured yet which also
- * implies GICv2.
- */
if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
irq->group = 1;
else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)
if (ret)
goto out;
+ /* Initialize groups on CPUs created before the VGIC type was known */
+ kvm_for_each_vcpu(i, vcpu, kvm) {
+ struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu;
+
+ for (i = 0; i < VGIC_NR_PRIVATE_IRQS; i++) {
+ struct vgic_irq *irq = &vgic_cpu->private_irqs[i];
+ irq->group = 1;
+ }
+ }
+
if (vgic_has_its(kvm)) {
ret = vgic_v4_init(kvm);
if (ret)
Sorry for the late reply.
I test the patch and it works. But I think there is randomness here.
1.vgic_init: set intid/27 group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq ----- it may exist.
4.vgic_mmio_write_group:## intid/27 group=1
I made an attempt before:
1. kvm_vgic_vcpu_init
according to if kvm_vgic_global_state.type == VGIC_V3, set group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq -----I really receive a vtimer irq, then the guest hangs.
thanks.
From: Christoffer Dall <hidden> Date: 2018-11-23 10:03:07
On Fri, Nov 23, 2018 at 02:01:56PM +0800, peng.hao2@zte.com.cn wrote:
quoted
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
struct vgic_irq *irq, int lr) if (vgic_irq_is_mapped_level(irq) &&
(val & ICH_LR_PENDING_BIT)) irq->line_level = false;
- if (irq->group)
+ if (model == KVM_DEV_TYPE_ARM_VGIC_V3)
This is not the right fix, not only because it basically reverts the
GICv3 part of 87322099052 (KVM: arm/arm64: vgic: Signal IRQs using
their configured group).
Can you try to work out why kvm_vgic_vcpu_init() is apparently called
before dist->vgic_model is set, also what value it has?
If I understand the code correctly, that shouldn't happen for a GICv3.
Even if the value of group is correctly assigned in kvm_vgic_vcpu_init, the group is then written 0 through >vgic_mmio_write_group.
If the interrupt comes at this time, the interrupt injection fails.
Does that mean that the guest is configuring its interrupts as Group0?
That sounds wrong, Linux should configure all it's interrupts as
non-secure group1.
no, I think that uefi dose this, not linux.
1. kvm_vgic_vcpu_init
2. vgic_create
3. kvm_vgic_dist_init
4.vgic_mmio_write_group: uefi as guest, write group=0
5.vgic_mmio_write_group: linux as guest, write group=1
Is this the same issue fixed by EDK2 commit:
66127011a544b90e ("ArmPkg/ArmGicDxe ARM: fix encoding for GICv3 interrupt acknowledge")
... where EDK2 would try to use IAR0 rather than IAR1?
The commit messages notes this lead to a boot-time hang.
I managed to trigger an issue with a really old EFI implementation that
doesn't configure its interrupts as Group1, and yet tries to ACK its
interrupts using the Group1 accessor. Guess what? It is not going to work.
Commit c7fefb690661f2e38afcb8200bd318ecf38ab961 in the edk2 tree seems
to be the fix (I only assume it does, I haven't actually checked). A
recent build, as found in Debian Buster, works perfectly (tested with
both QEMU v2.12 and tip of tree).
Now, I really don't get what you're saying about Linux not getting
interrupts. How do you get to booting Linux if EFI is not making any
forward progress? Are you trying them independently?
I start linux with bypassing uefi, the print info is the same.
[507107.748908] vgic_mmio_write_group:## intid/27 group=0
[507107.752185] vgic_mmio_write_group:## intid/27 group=0
[507107.899566] vgic_mmio_write_group:## intid/27 group=1
[507107.907370] vgic_mmio_write_group:## intid/27 group=1
the command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -kernel /home/kernelboot/vmlinuz-4.16.0+ -initrd /home/kernelboot/initramfs-4.16.0+.img -append root=/dev/mapper/cla-root ro crashkernel=auto rd.lvm.lv=cla/root rd.lvm.lv=cla/swap.UTF-8 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg >timestamp=on
This is strange. That's probably the Linux 4.16 kernel setting group to 0, and I'll continue to track in guest.
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)
irq->config = VGIC_CONFIG_LEVEL;
}
- /*
- * GICv3 can only be created via the KVM_DEVICE_CREATE API and
- * so we always know the emulation type at this point as it's
- * either explicitly configured as GICv3, or explicitly
- * configured as GICv2, or not configured yet which also
- * implies GICv2.
- */
if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
irq->group = 1;
else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)
if (ret)
goto out;
+ /* Initialize groups on CPUs created before the VGIC type was known */
+ kvm_for_each_vcpu(i, vcpu, kvm) {
+ struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu;
+
+ for (i = 0; i < VGIC_NR_PRIVATE_IRQS; i++) {
+ struct vgic_irq *irq = &vgic_cpu->private_irqs[i];
+ irq->group = 1;
+ }
+ }
+
if (vgic_has_its(kvm)) {
ret = vgic_v4_init(kvm);
if (ret)
Sorry for the late reply.
I test the patch and it works. But I think there is randomness here.
1.vgic_init: set intid/27 group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq ----- it may exist.
4.vgic_mmio_write_group:## intid/27 group=1
Are these writes from userspace or from the guest?
(I assume they're from the guest.)
I made an attempt before:
Was this previous experiment using my patch or without my patch?
1. kvm_vgic_vcpu_init
according to if kvm_vgic_global_state.type == VGIC_V3, set group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq -----I really receive a vtimer irq, then the guest hangs.
If the guest you're using is flipping the group of the interrupt and yet
enabling the device and interrupt while flipping the group, then it's
not expected to work and it's a guest bug.
My hunch here tells me that my patch is what we need for KVM, and either
(1) You no longer have a problem but are tracing some guest
initialization behavior which is fine, or
(2) You still have a problem because you also have some broken guest
code (guest UEFI or guest Linux) that also needs fixing.
If you can demonstrate that you still have a problem, with my path
applied to KVM, and with a recent guest Linux and guest UEFI, then I'll
be happy to have another look. In that case, could you please provide
the exact versions of your guest Linux and UEFI, as well as the QEMU
version and command line.
Thanks,
Christoffer
Hi,
On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 19/11/2018 09:10, Mark Rutland wrote:
quoted
On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.hao2@zte.com.cn wrote:
quoted
quoted
On 16/11/18 00:23, peng.hao2@zte.com.cn wrote:
quoted
quoted
Hi,
quoted
When virtual machine starts, hang up.
I take it you mean the *guest* hangs? Because it doesn't get a timer
interrupt?
quoted
The kernel version of guest
is 4.16. Host support vgic_v3.
Your host kernel is something recent, I guess?
quoted
It was mainly due to the incorrect vgic_irq's(intid=27) group value
during injection interruption. when kvm_vgic_vcpu_init is called,
dist is not initialized at this time. Unable to get vgic V3 or V2
correctly, so group is not set.
Mmh, that shouldn't happen with (v)GICv3. Do you use QEMU (which
version?) or some other userland tool?
QEMU emulator version 3.0.50 .
quoted
quoted
group is setted to 1 when vgic_mmio_write_group is invoked at some
time.
when irq->group=0 (intid=27), No ICH_LR_GROUP flag was set and
interrupt injection failed.
Signed-off-by: Peng Hao <redacted>
---
virt/kvm/arm/vgic/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -231,13 +231,6 @@ int kvm_vgic_vcpu_init(struct kvm_vcpu *vcpu)
irq->config = VGIC_CONFIG_LEVEL;
}
- /*
- * GICv3 can only be created via the KVM_DEVICE_CREATE API and
- * so we always know the emulation type at this point as it's
- * either explicitly configured as GICv3, or explicitly
- * configured as GICv2, or not configured yet which also
- * implies GICv2.
- */
if (dist->vgic_model == KVM_DEV_TYPE_ARM_VGIC_V3)
irq->group = 1;
else
@@ -298,6 +291,16 @@ int vgic_init(struct kvm *kvm)
if (ret)
goto out;
+ /* Initialize groups on CPUs created before the VGIC type was known */
+ kvm_for_each_vcpu(i, vcpu, kvm) {
+ struct vgic_cpu *vgic_cpu = &vcpu->arch.vgic_cpu;
+
+ for (i = 0; i < VGIC_NR_PRIVATE_IRQS; i++) {
+ struct vgic_irq *irq = &vgic_cpu->private_irqs[i];
+ irq->group = 1;
+ }
+ }
+
if (vgic_has_its(kvm)) {
ret = vgic_v4_init(kvm);
if (ret)
Sorry for the late reply.
I test the patch and it works. But I think there is randomness here.
1.vgic_init: set intid/27 group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq ----- it may exist.
4.vgic_mmio_write_group:## intid/27 group=1
Are these writes from userspace or from the guest?
(I assume they're from the guest.)
quoted
I made an attempt before:
Was this previous experiment using my patch or without my patch?
1. kvm_vgic_vcpu_init
according to if kvm_vgic_global_state.type == VGIC_V3, set group=1
2.vgic_mmio_write_group:## intid/27 group=0
3.!!! receive a vtimer irq -----I really receive a vtimer irq, then the guest hangs.
If the guest you're using is flipping the group of the interrupt and yet
enabling the device and interrupt while flipping the group, then it's
not expected to work and it's a guest bug.
My hunch here tells me that my patch is what we need for KVM, and either
(1) You no longer have a problem but are tracing some guest
initialization behavior which is fine, or
(2) You still have a problem because you also have some broken guest
code (guest UEFI or guest Linux) that also needs fixing.
If you can demonstrate that you still have a problem, with my path
applied to KVM, and with a recent guest Linux and guest UEFI, then I'll
be happy to have another look. In that case, could you please provide
the exact versions of your guest Linux and UEFI, as well as the QEMU
version and command line.
I'm sorry I make a mistake.I updated UEFI but never had time to test it. Yesterday I merged your patch
to test, but forgot that I had updated UEFI.
Here are the corrected test results :
-----------------------------------------------------------------------------------------
|_new uefi + your patch_____________|______guest start normally__|
|_old uefi + your patch______________|______guest hangs________|
|_bypass uefi _(with/without your patch)|______guest start normally__|
|_new uefi + without your patch ______|______guest start normally_ |
|_old uefi + without your patch_ ______| _____ guest hangs________|
So the problem seems to be in UEFI. new uefi can be sure there is no a irq between
the group=0 and group=1 from vgic_mmio_write_group.
guest kernel :4.16.0 (commit c18bb396d3d261ebbb4efbc05129c5d354c541e4)
the version of guest old uefi corresponds to qemu 3.0.50.
the version of new uefi is the latest edk2.
I use libvirt to start guest, and the qemu command line is like this:
/home/qemu-patch/linshi/qemu/aarch64-softmmu/qemu-system-aarch64 -name guest=centos74-ph-1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-centos74-ph-1/master-key.aes -machine virt-3.1,accel=kvm,usb=off,dump-guest-core=off,gic-version=3 -cpu host -drive file=/usr/share/AAVMF/AAVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/var/lib/libvirt/qemu/nvram/centos74-ph-1_VARS.fd,if=pflash,format=raw,unit=1 -m 4096 -realtime mlock=off -smp 4,maxcpus=8,sockets=8,cores=1,threads=1 -uuid ff5ecf4e-1234-425f-948d-8d91135e109c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-centos74-ph-1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1 -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x0 -device pcie-root-port,port=0x10,chassis=3,id=pci.3,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x1 -device usb-ehci,id=usb,bus=pci.2,addr=0x1 -device piix3-usb-uhci,id=usb1,bus=pci.2,addr=0x2 -device virtio-scsi-device,id=scsi0 -device virtio-serial-device,id=virtio-serial0 -drive file=/home/centos74-ph/boot.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -drive file=/home/centos74-ph/data.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-1 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=1,drive=drive-scsi0-0-0-1,id=scsi0-0-0-1 -drive file=/home/CentOS-7-aarch64-Everything.iso,format=raw,if=none,id=drive-scsi0-0-0-2,readonly=on -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=2,drive=drive-scsi0-0-0-2,id=scsi0-0-0-2,bootindex=2 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-device,netdev=hostnet0,id=net0,mac=aa:35:97:5b:33:ac -add-fd set=2,fd=30 -chardev pty,id=charserial0,logfile=/dev/fdset/2,logappend=on -serial chardev:charserial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/centos74.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -device usb-kbd,id=input1,bus=usb.0,port=2 -vnc 0.0.0.0:0 -k en-us -device virtio-gpu-pci,id=video0,max_outputs=1,bus=pci.3,addr=0x0 -device pvpanic-mmio -msg timestamp=on
Thanks.