brintos

brintos / linux-shallow public Read only

0
0
Text · 6.6 KiB · 3066fea Raw
188 lines · plain
1What:		/sys/bus/vmbus/hibernation2Date:		Jan 20213KernelVersion:	5.124Contact:	Dexuan Cui <decui@microsoft.com>5Description:	Whether the host supports hibernation for the VM.6Users:		Daemon that sets up swap partition/file for hibernation.7 8What:		/sys/bus/vmbus/devices/<UUID>/id9Date:		Jul 200910KernelVersion:	2.6.3111Contact:	K. Y. Srinivasan <kys@microsoft.com>12Description:	The VMBus child_relid of the device's primary channel13Users:		tools/hv/lsvmbus14 15What:		/sys/bus/vmbus/devices/<UUID>/class_id16Date:		Jul 200917KernelVersion:	2.6.3118Contact:	K. Y. Srinivasan <kys@microsoft.com>19Description:	The VMBus interface type GUID of the device20Users:		tools/hv/lsvmbus21 22What:		/sys/bus/vmbus/devices/<UUID>/device_id23Date:		Jul 200924KernelVersion:	2.6.3125Contact:	K. Y. Srinivasan <kys@microsoft.com>26Description:	The VMBus interface instance GUID of the device27Users:		tools/hv/lsvmbus28 29What:		/sys/bus/vmbus/devices/<UUID>/channel_vp_mapping30Date:		Jul 201531KernelVersion:	4.2.032Contact:	K. Y. Srinivasan <kys@microsoft.com>33Description:	The mapping of which primary/sub channels are bound to which34		Virtual Processors.35		Format: <channel's child_relid:the bound cpu's number>36Users:		tools/hv/lsvmbus37 38What:		/sys/bus/vmbus/devices/<UUID>/device39Date:		Dec. 201540KernelVersion:	4.541Contact:	K. Y. Srinivasan <kys@microsoft.com>42Description:	The 16 bit device ID of the device43Users:		tools/hv/lsvmbus and user level RDMA libraries44 45What:		/sys/bus/vmbus/devices/<UUID>/vendor46Date:		Dec. 201547KernelVersion:	4.548Contact:	K. Y. Srinivasan <kys@microsoft.com>49Description:	The 16 bit vendor ID of the device50Users:		tools/hv/lsvmbus and user level RDMA libraries51 52What:		/sys/bus/vmbus/devices/<UUID>/numa_node53Date:		Jul 201854KernelVersion:	4.1955Contact:	Stephen Hemminger <sthemmin@microsoft.com>56Description:	This NUMA node to which the VMBUS device is57		attached, or -1 if the node is unknown.58 59What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>60Date:		September. 201761KernelVersion:	4.1462Contact:	Stephen Hemminger <sthemmin@microsoft.com>63Description:	Directory for per-channel information64		NN is the VMBUS relid associated with the channel.65 66What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/cpu67Date:		September. 201768KernelVersion:	4.1469Contact:	Stephen Hemminger <sthemmin@microsoft.com>70Description:	VCPU (sub)channel is affinitized to71Users:		tools/hv/lsvmbus and other debugging tools72 73What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/in_mask74Date:		September. 201775KernelVersion:	4.1476Contact:	Stephen Hemminger <sthemmin@microsoft.com>77Description:	Host to guest channel interrupt mask78Users:		Debugging tools79 80What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/latency81Date:		September. 201782KernelVersion:	4.1483Contact:	Stephen Hemminger <sthemmin@microsoft.com>84Description:	Channel signaling latency. This file is available only for85		performance critical channels (storage, network, etc.) that use86		the monitor page mechanism.87Users:		Debugging tools88 89What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/out_mask90Date:		September. 201791KernelVersion:	4.1492Contact:	Stephen Hemminger <sthemmin@microsoft.com>93Description:	Guest to host channel interrupt mask94Users:		Debugging tools95 96What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/pending97Date:		September. 201798KernelVersion:	4.1499Contact:	Stephen Hemminger <sthemmin@microsoft.com>100Description:	Channel interrupt pending state. This file is available only for101		performance critical channels (storage, network, etc.) that use102		the monitor page mechanism.103Users:		Debugging tools104 105What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/read_avail106Date:		September. 2017107KernelVersion:	4.14108Contact:	Stephen Hemminger <sthemmin@microsoft.com>109Description:	Bytes available to read110Users:		Debugging tools111 112What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/write_avail113Date:		September. 2017114KernelVersion:	4.14115Contact:	Stephen Hemminger <sthemmin@microsoft.com>116Description:	Bytes available to write117Users:		Debugging tools118 119What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/events120Date:		September. 2017121KernelVersion:	4.14122Contact:	Stephen Hemminger <sthemmin@microsoft.com>123Description:	Number of times we have signaled the host124Users:		Debugging tools125 126What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/interrupts127Date:		September. 2017128KernelVersion:	4.14129Contact:	Stephen Hemminger <sthemmin@microsoft.com>130Description:	Number of times we have taken an interrupt (incoming)131Users:		Debugging tools132 133What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/subchannel_id134Date:		January. 2018135KernelVersion:	4.16136Contact:	Stephen Hemminger <sthemmin@microsoft.com>137Description:	Subchannel ID associated with VMBUS channel138Users:		Debugging tools and userspace drivers139 140What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/monitor_id141Date:		January. 2018142KernelVersion:	4.16143Contact:	Stephen Hemminger <sthemmin@microsoft.com>144Description:	Monitor bit associated with channel. This file is available only145		for performance critical channels (storage, network, etc.) that146		use the monitor page mechanism.147Users:		Debugging tools and userspace drivers148 149What:		/sys/bus/vmbus/devices/<UUID>/channels/<N>/ring150Date:		January. 2018151KernelVersion:	4.16152Contact:	Stephen Hemminger <sthemmin@microsoft.com>153Description:	Binary file created by uio_hv_generic for ring buffer154Users:		Userspace drivers155 156What:           /sys/bus/vmbus/devices/<UUID>/channels/<N>/intr_in_full157Date:           February 2019158KernelVersion:  5.0159Contact:        Michael Kelley <mikelley@microsoft.com>160Description:    Number of guest to host interrupts caused by the inbound ring161		buffer transitioning from full to not full while a packet is162		waiting for buffer space to become available163Users:          Debugging tools164 165What:           /sys/bus/vmbus/devices/<UUID>/channels/<N>/intr_out_empty166Date:           February 2019167KernelVersion:  5.0168Contact:        Michael Kelley <mikelley@microsoft.com>169Description:    Number of guest to host interrupts caused by the outbound ring170		buffer transitioning from empty to not empty171Users:          Debugging tools172 173What:           /sys/bus/vmbus/devices/<UUID>/channels/<N>/out_full_first174Date:           February 2019175KernelVersion:  5.0176Contact:        Michael Kelley <mikelley@microsoft.com>177Description:    Number of write operations that were the first to encounter an178		outbound ring buffer full condition179Users:          Debugging tools180 181What:           /sys/bus/vmbus/devices/<UUID>/channels/<N>/out_full_total182Date:           February 2019183KernelVersion:  5.0184Contact:        Michael Kelley <mikelley@microsoft.com>185Description:    Total number of write operations that encountered an outbound186		ring buffer full condition187Users:          Debugging tools188