0001 What: /sys/devices/*/xenbus/event_channels
0002 Date: February 2021
0003 Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>
0004 Description:
0005 Number of Xen event channels associated with a kernel based
0006 paravirtualized device frontend or backend.
0007
0008 What: /sys/devices/*/xenbus/events
0009 Date: February 2021
0010 Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>
0011 Description:
0012 Total number of Xen events received for a Xen pv device
0013 frontend or backend.
0014
0015 What: /sys/devices/*/xenbus/jiffies_eoi_delayed
0016 Date: February 2021
0017 Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>
0018 Description:
0019 Summed up time in jiffies the EOI of an interrupt for a Xen
0020 pv device has been delayed in order to avoid stalls due to
0021 event storms. This value rising is a first sign for a rogue
0022 other end of the pv device.
0023
0024 What: /sys/devices/*/xenbus/spurious_events
0025 Date: February 2021
0026 Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>
0027 Description:
0028 Number of events received for a Xen pv device which did not
0029 require any action. Too many spurious events in a row will
0030 trigger delayed EOI processing.
0031
0032 What: /sys/devices/*/xenbus/spurious_threshold
0033 Date: February 2021
0034 Contact: Xen Developers mailing list <xen-devel@lists.xenproject.org>
0035 Description:
0036 Controls the tolerated number of subsequent spurious events
0037 before delayed EOI processing is triggered for a Xen pv
0038 device. Default is 1. This can be modified in case the other
0039 end of the pv device is issuing spurious events on a regular
0040 basis and is known not to be malicious on purpose. Raising
0041 the value for such cases can improve pv device performance.
