1What: /sys/devices/*/xenbus/event_channels 2Date: February 2021 3Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org> 4Description: 5 Number of Xen event channels associated with a kernel based 6 paravirtualized device frontend or backend. 7 8What: /sys/devices/*/xenbus/events 9Date: February 2021 10Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org> 11Description: 12 Total number of Xen events received for a Xen pv device 13 frontend or backend. 14 15What: /sys/devices/*/xenbus/jiffies_eoi_delayed 16Date: February 2021 17Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org> 18Description: 19 Summed up time in jiffies the EOI of an interrupt for a Xen 20 pv device has been delayed in order to avoid stalls due to 21 event storms. This value rising is a first sign for a rogue 22 other end of the pv device. 23 24What: /sys/devices/*/xenbus/spurious_events 25Date: February 2021 26Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org> 27Description: 28 Number of events received for a Xen pv device which did not 29 require any action. Too many spurious events in a row will 30 trigger delayed EOI processing. 31 32What: /sys/devices/*/xenbus/spurious_threshold 33Date: February 2021 34Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org> 35Description: 36 Controls the tolerated number of subsequent spurious events 37 before delayed EOI processing is triggered for a Xen pv 38 device. Default is 1. This can be modified in case the other 39 end of the pv device is issuing spurious events on a regular 40 basis and is known not to be malicious on purpose. Raising 41 the value for such cases can improve pv device performance. 42