提交 8103b4d1 编写于 作者: A Alexander Graf 提交者: Aurelien Jarno

s390x: Dispatch interrupts to KVM or the real CPU

The KVM interrupt injection path is non-generic for now. So we need to push
knowledge of how to inject a device interrupt using KVM into the actual device
code.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>
上级 3110e292
......@@ -43,6 +43,8 @@
do { } while (0)
#endif
#define VIRTIO_EXT_CODE 0x2603
struct BusInfo s390_virtio_bus_info = {
.name = "s390-virtio",
.size = sizeof(VirtIOS390Bus),
......@@ -305,9 +307,13 @@ static void virtio_s390_notify(void *opaque, uint16_t vector)
{
VirtIOS390Device *dev = (VirtIOS390Device*)opaque;
uint64_t token = s390_virtio_device_vq_token(dev, vector);
CPUState *env = s390_cpu_addr2state(0);
/* XXX kvm dependency! */
kvm_s390_virtio_irq(s390_cpu_addr2state(0), 0, token);
if (kvm_enabled()) {
kvm_s390_virtio_irq(env, 0, token);
} else {
cpu_inject_ext(env, VIRTIO_EXT_CODE, 0, token);
}
}
static unsigned virtio_s390_get_features(void *opaque)
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册