[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Possible bug on ARM with irq passthrough

  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: Ivan Pavić2 <Ivan.Pavic2@xxxxxx>
  • Date: Tue, 4 Jul 2017 20:20:09 +0000
  • Accept-language: en-US
  • Delivery-date: Tue, 04 Jul 2017 20:20:16 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AQHS9P6UHBNKq/qvD02hcZoQ2JKzlQ==
  • Thread-topic: [Xen-devel] Possible bug on ARM with irq passthrough


I'm testing IRQ latency on exynos5422. I'm using Xen 4.10-unstable. I used 
device passthrough for SPI irq 64. For guest domain I used  FreeRTOS. When I 
use credit scheduler after destruction of domain, IRQ is released. I changed 
scheduler to credit2 and rtds at boot time and IRQ wasn't released after 
destruction. xl create dom-free-rtos.cfg fails with:

libxl: error: libxl_create.c:1278:domcreate_launch_dm: Domain 5:failed give 
domain access to irq 64: Device or resource busy

This is very strange because it doesn't happen with credit scheduler. This is 
output of xl dmesg:

(XEN) IRQ 64 is already used by domain 1

Everything works first time but when I destroy domain and try to create again 
it fails. It works normally with credit scheduler. In dom-free-rtos.cfg:
irqs = [64]

Ivan Pavic

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.