This patch introduces vGPU interrupt emulation framework. The vGPU intrerrupt emulation framework is an event-based interrupt emulation framework. It's responsible for emulating GEN hardware interrupts during emulating other HW behaviour. It consists several components: - Descriptions of interrupt register bit - Upper level <-> lower level interrupt mapping - GEN HW IER/IMR/IIR register emulation routines - Event-based interrupt propagation interface When a GVT-g component wants to inject an interrupt to a VM during a emulation, first it should specify the event needs to be emulated and the framework will deal with the rest of emulation: - Generating related virtual IIR bit according to virtual IER and IMRs, - Generate related virtual upper level virtual IIR bit accodring to the per-platform interrupt mapping - Injecting a MSI to VM Signed-off-by: Zhi Wang <zhi.a.wang@intel.com> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
121 lines
3.7 KiB
C
121 lines
3.7 KiB
C
/*
|
|
* Copyright(c) 2011-2016 Intel Corporation. All rights reserved.
|
|
*
|
|
* Permission is hereby granted, free of charge, to any person obtaining a
|
|
* copy of this software and associated documentation files (the "Software"),
|
|
* to deal in the Software without restriction, including without limitation
|
|
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
|
|
* and/or sell copies of the Software, and to permit persons to whom the
|
|
* Software is furnished to do so, subject to the following conditions:
|
|
*
|
|
* The above copyright notice and this permission notice (including the next
|
|
* paragraph) shall be included in all copies or substantial portions of the
|
|
* Software.
|
|
*
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
|
|
* THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
* SOFTWARE.
|
|
*
|
|
* Authors:
|
|
* Eddie Dong <eddie.dong@intel.com>
|
|
* Dexuan Cui
|
|
* Jike Song <jike.song@intel.com>
|
|
*
|
|
* Contributors:
|
|
* Zhi Wang <zhi.a.wang@intel.com>
|
|
*
|
|
*/
|
|
|
|
#ifndef _GVT_MPT_H_
|
|
#define _GVT_MPT_H_
|
|
|
|
/**
|
|
* DOC: Hypervisor Service APIs for GVT-g Core Logic
|
|
*
|
|
* This is the glue layer between specific hypervisor MPT modules and GVT-g core
|
|
* logic. Each kind of hypervisor MPT module provides a collection of function
|
|
* callbacks and will be attached to GVT host when the driver is loading.
|
|
* GVT-g core logic will call these APIs to request specific services from
|
|
* hypervisor.
|
|
*/
|
|
|
|
/**
|
|
* intel_gvt_hypervisor_detect_host - check if GVT-g is running within
|
|
* hypervisor host/privilged domain
|
|
*
|
|
* Returns:
|
|
* Zero on success, -ENODEV if current kernel is running inside a VM
|
|
*/
|
|
static inline int intel_gvt_hypervisor_detect_host(void)
|
|
{
|
|
return intel_gvt_host.mpt->detect_host();
|
|
}
|
|
|
|
/**
|
|
* intel_gvt_hypervisor_attach_vgpu - call hypervisor to initialize vGPU
|
|
* related stuffs inside hypervisor.
|
|
*
|
|
* Returns:
|
|
* Zero on success, negative error code if failed.
|
|
*/
|
|
static inline int intel_gvt_hypervisor_attach_vgpu(struct intel_vgpu *vgpu)
|
|
{
|
|
return intel_gvt_host.mpt->attach_vgpu(vgpu, &vgpu->handle);
|
|
}
|
|
|
|
/**
|
|
* intel_gvt_hypervisor_detach_vgpu - call hypervisor to release vGPU
|
|
* related stuffs inside hypervisor.
|
|
*
|
|
* Returns:
|
|
* Zero on success, negative error code if failed.
|
|
*/
|
|
static inline void intel_gvt_hypervisor_detach_vgpu(struct intel_vgpu *vgpu)
|
|
{
|
|
intel_gvt_host.mpt->detach_vgpu(vgpu->handle);
|
|
}
|
|
|
|
#define MSI_CAP_CONTROL(offset) (offset + 2)
|
|
#define MSI_CAP_ADDRESS(offset) (offset + 4)
|
|
#define MSI_CAP_DATA(offset) (offset + 8)
|
|
#define MSI_CAP_EN 0x1
|
|
|
|
/**
|
|
* intel_gvt_hypervisor_inject_msi - inject a MSI interrupt into vGPU
|
|
*
|
|
* Returns:
|
|
* Zero on success, negative error code if failed.
|
|
*/
|
|
static inline int intel_gvt_hypervisor_inject_msi(struct intel_vgpu *vgpu)
|
|
{
|
|
unsigned long offset = vgpu->gvt->device_info.msi_cap_offset;
|
|
u16 control, data;
|
|
u32 addr;
|
|
int ret;
|
|
|
|
control = *(u16 *)(vgpu_cfg_space(vgpu) + MSI_CAP_CONTROL(offset));
|
|
addr = *(u32 *)(vgpu_cfg_space(vgpu) + MSI_CAP_ADDRESS(offset));
|
|
data = *(u16 *)(vgpu_cfg_space(vgpu) + MSI_CAP_DATA(offset));
|
|
|
|
/* Do not generate MSI if MSIEN is disable */
|
|
if (!(control & MSI_CAP_EN))
|
|
return 0;
|
|
|
|
if (WARN(control & GENMASK(15, 1), "only support one MSI format\n"))
|
|
return -EINVAL;
|
|
|
|
gvt_dbg_irq("vgpu%d: inject msi address %x data%x\n", vgpu->id, addr,
|
|
data);
|
|
|
|
ret = intel_gvt_host.mpt->inject_msi(vgpu->handle, addr, data);
|
|
if (ret)
|
|
return ret;
|
|
return 0;
|
|
}
|
|
|
|
#endif /* _GVT_MPT_H_ */
|