42 lines · plain
1What: /sys/devices/*/xenbus/event_channels2Date: February 20213Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>4Description:5 Number of Xen event channels associated with a kernel based6 paravirtualized device frontend or backend.7 8What: /sys/devices/*/xenbus/events9Date: February 202110Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>11Description:12 Total number of Xen events received for a Xen pv device13 frontend or backend.14 15What: /sys/devices/*/xenbus/jiffies_eoi_delayed16Date: February 202117Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>18Description:19 Summed up time in jiffies the EOI of an interrupt for a Xen20 pv device has been delayed in order to avoid stalls due to21 event storms. This value rising is a first sign for a rogue22 other end of the pv device.23 24What: /sys/devices/*/xenbus/spurious_events25Date: February 202126Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>27Description:28 Number of events received for a Xen pv device which did not29 require any action. Too many spurious events in a row will30 trigger delayed EOI processing.31 32What: /sys/devices/*/xenbus/spurious_threshold33Date: February 202134Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>35Description:36 Controls the tolerated number of subsequent spurious events37 before delayed EOI processing is triggered for a Xen pv38 device. Default is 1. This can be modified in case the other39 end of the pv device is issuing spurious events on a regular40 basis and is known not to be malicious on purpose. Raising41 the value for such cases can improve pv device performance.42