kvm fpu warning on 4.14.89

Jan Kiszka jan.kiszka at siemens.com
Thu Mar 21 09:01:11 CET 2019


On 21.03.19 08:04, cagnulein wrote:
> I've got a similar issue even with the 4.9.146 with a kvm guest on and latency 
> on too. It's quite deterministic. Any idea?
>

I didn't trigger your trace yet, but I can know study this splash:

[  140.794470] I-pipe: Detected illicit call from head domain 'Xenomai'
[  140.794470]         into a regular Linux service
[  140.797855] CPU: 0 PID: 1021 Comm: qemu-system-x86 Not tainted 4.14.103+ #43
[  140.799644] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 
rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org 04/01/2014
[  140.799648] I-pipe domain: Xenomai
[  140.799650] Call Trace:
[  140.799654]  <IRQ>
[  140.799670]  ipipe_root_only+0xfe/0x130
[  140.799678]  ipipe_stall_root+0xe/0x60
[  140.799685]  lock_acquire+0x62/0x1a0
[  140.799692]  ? __switch_to_asm+0x40/0x70
[  140.799703]  kvm_arch_vcpu_put+0xb0/0x1a0
[  140.799707]  ? kvm_arch_vcpu_put+0x6e/0x1a0
[  140.799717]  __ipipe_handle_vm_preemption+0x2a/0x50
[  140.799723]  ___xnsched_run.part.76+0x371/0x590
[  140.799733]  xnintr_core_clock_handler+0x3f5/0x420
[  140.799745]  dispatch_irq_head+0x9a/0x150
[  140.799757]  __ipipe_handle_irq+0x7e/0x210
[  140.799768]  apic_timer_interrupt+0x7f/0xb0
[...]

Will let you know when I have details.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux



More information about the Xenomai mailing list