Xiangyang Wu dec8d7e22f hv: support at most MAX_VUART_NUM_PER_VM legacy vuarts ... In the current hypervisor, only support at most two legacy vuarts (COM1 and COM2) for a VM, COM1 is usually configured as VM console, COM2 is configured as communication channel of S5 feature. Hypervisor can support MAX_VUART_NUM_PER_VM(8) legacy vuart, but only register handlers for two legacy vuart since the assumption (legacy vuart is less than 2) is made. In the current hypervisor configurtion, io port (2F8H) is always allocated for virtual COM2, it will be not friendly if user wants to assign this port to physical COM2. Legacy vuart is common communication channel between service VM and user VM, it can work in polling mode and its driver exits in each guest OS. The channel can be used to send shutdown command to user VM in S5 featuare, so need to config serval vuarts for service VM and one vuart for each user VM. The following changes will be made to support at most MAX_VUART_NUM_PER_VM legacy vuarts: - Refine legacy vuarts initialization to register PIO handler for related vuart. - Update assumption of legacy vuart number. BTW, config tools updates about legacy vuarts will be made in other patch. v1-->v2: Update commit message to make this patch's purpose clearer; If vuart index is valid, register handler for it. Tracked-On: #6652 Signed-off-by: Xiangyang Wu <xiangyang.wu@intel.com> Acked-by: Eddie Dong <eddie.dong@Intel.com>		2021-10-15 10:00:02 +08:00
..
asm	hv: support at most MAX_VUART_NUM_PER_VM legacy vuarts	2021-10-15 10:00:02 +08:00