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