QEMU源码全解析 —— virtio（8）

2023-12-15 23:36
文章标签 源码 解析 qemu virtio

本文主要是介绍QEMU源码全解析 —— virtio（8），希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

接前一篇文章：

上一回讲解了virtio balloon相关类所涉及的realize函数，如下表所示：

realize函数parent_dc_realize函数
DeviceClassvirtio_pci_dc_realize
PCIDeviceClassvirtio_pci_realize
VirtioPCIClassvirtio_balloon_pci_realizepci_qdev_realize

本回继续接着讲。

再来回顾一下，virtio balloon PCI代理设备类型的初始化函数virtio_balloon_pci_class_init()，在hw/virtio/virtio-balloon-pci.c中，代码如下：

static void virtio_balloon_pci_class_init(ObjectClass *klass, void *data)
{DeviceClass *dc = DEVICE_CLASS(klass);VirtioPCIClass *k = VIRTIO_PCI_CLASS(klass);PCIDeviceClass *pcidev_k = PCI_DEVICE_CLASS(klass);k->realize = virtio_balloon_pci_realize;set_bit(DEVICE_CATEGORY_MISC, dc->categories);pcidev_k->vendor_id = PCI_VENDOR_ID_REDHAT_QUMRANET;pcidev_k->device_id = PCI_DEVICE_ID_VIRTIO_BALLOON;pcidev_k->revision = VIRTIO_PCI_ABI_VERSION;pcidev_k->class_id = PCI_CLASS_OTHERS;
}

device_set_realized函数在hw/virtio/virtio-balloon-pci.c中，代码如下：

static void device_set_realized(Object *obj, bool value, Error **errp)
{DeviceState *dev = DEVICE(obj);DeviceClass *dc = DEVICE_GET_CLASS(dev);HotplugHandler *hotplug_ctrl;BusState *bus;NamedClockList *ncl;Error *local_err = NULL;bool unattached_parent = false;static int unattached_count;if (dev->hotplugged && !dc->hotpluggable) {error_setg(errp, QERR_DEVICE_NO_HOTPLUG, object_get_typename(obj));return;}if (value && !dev->realized) {if (!check_only_migratable(obj, errp)) {goto fail;}if (!obj->parent) {gchar *name = g_strdup_printf("device[%d]", unattached_count++);object_property_add_child(container_get(qdev_get_machine(),"/unattached"),name, obj);unattached_parent = true;g_free(name);}hotplug_ctrl = qdev_get_hotplug_handler(dev);if (hotplug_ctrl) {hotplug_handler_pre_plug(hotplug_ctrl, dev, &local_err);if (local_err != NULL) {goto fail;}}if (dc->realize) {dc->realize(dev, &local_err);if (local_err != NULL) {goto fail;}}DEVICE_LISTENER_CALL(realize, Forward, dev);/** always free/re-initialize here since the value cannot be cleaned up* in device_unrealize due to its usage later on in the unplug path*/g_free(dev->canonical_path);dev->canonical_path = object_get_canonical_path(OBJECT(dev));QLIST_FOREACH(ncl, &dev->clocks, node) {if (ncl->alias) {continue;} else {clock_setup_canonical_path(ncl->clock);}}if (qdev_get_vmsd(dev)) {if (vmstate_register_with_alias_id(VMSTATE_IF(dev),VMSTATE_INSTANCE_ID_ANY,qdev_get_vmsd(dev), dev,dev->instance_id_alias,dev->alias_required_for_version,&local_err) < 0) {goto post_realize_fail;}}/** Clear the reset state, in case the object was previously unrealized* with a dirty state.*/resettable_state_clear(&dev->reset);QLIST_FOREACH(bus, &dev->child_bus, sibling) {if (!qbus_realize(bus, errp)) {goto child_realize_fail;}}if (dev->hotplugged) {/** Reset the device, as well as its subtree which, at this point,* should be realized too.*/resettable_assert_reset(OBJECT(dev), RESET_TYPE_COLD);resettable_change_parent(OBJECT(dev), OBJECT(dev->parent_bus),NULL);resettable_release_reset(OBJECT(dev), RESET_TYPE_COLD);}dev->pending_deleted_event = false;if (hotplug_ctrl) {hotplug_handler_plug(hotplug_ctrl, dev, &local_err);if (local_err != NULL) {goto child_realize_fail;}}qatomic_store_release(&dev->realized, value);} else if (!value && dev->realized) {/** Change the value so that any concurrent users are aware* that the device is going to be unrealized** TODO: change .realized property to enum that states* each phase of the device realization/unrealization*/qatomic_set(&dev->realized, value);/** Ensure that concurrent users see this update prior to* any other changes done by unrealize.*/smp_wmb();QLIST_FOREACH(bus, &dev->child_bus, sibling) {qbus_unrealize(bus);}if (qdev_get_vmsd(dev)) {vmstate_unregister(VMSTATE_IF(dev), qdev_get_vmsd(dev), dev);}if (dc->unrealize) {dc->unrealize(dev);}dev->pending_deleted_event = true;DEVICE_LISTENER_CALL(unrealize, Reverse, dev);}assert(local_err == NULL);return;child_realize_fail:QLIST_FOREACH(bus, &dev->child_bus, sibling) {qbus_unrealize(bus);}if (qdev_get_vmsd(dev)) {vmstate_unregister(VMSTATE_IF(dev), qdev_get_vmsd(dev), dev);}post_realize_fail:g_free(dev->canonical_path);dev->canonical_path = NULL;if (dc->unrealize) {dc->unrealize(dev);}fail:error_propagate(errp, local_err);if (unattached_parent) {/** Beware, this doesn't just revert* object_property_add_child(), it also runs bus_remove()!*/object_unparent(OBJECT(dev));unattached_count--;}
}

设置virtio PCI代理设备的realize属性时，device_set_realized函数中会首先调用DeviceClass->realize函数指针所指向的函数，也就是virtio_pci_dc_realize函数。代码片段如下：

        if (dc->realize) {dc->realize(dev, &local_err);if (local_err != NULL) {goto fail;}}

virtio_pci_dc_realize函数在hw/virtio/virtio-pci.c中，代码如下：

static void virtio_pci_dc_realize(DeviceState *qdev, Error **errp)
{VirtioPCIClass *vpciklass = VIRTIO_PCI_GET_CLASS(qdev);VirtIOPCIProxy *proxy = VIRTIO_PCI(qdev);PCIDevice *pci_dev = &proxy->pci_dev;if (!(proxy->flags & VIRTIO_PCI_FLAG_DISABLE_PCIE) &&virtio_pci_modern(proxy)) {pci_dev->cap_present |= QEMU_PCI_CAP_EXPRESS;}vpciklass->parent_dc_realize(qdev, errp);
}

virtio_pci_dc_realize函数中会调用VirtioPCIClass->parent_dc_realize，也就是pci_qdev_realize函数。在pci_qdev_realize函数中会调用PCIDeviceClass的realize函数指针所指向的函数，也就是virtio_pci_realize函数。virtio_pci_realize函数在hw/virtio/virtio-pci.c中，代码如下：

static void virtio_pci_realize(PCIDevice *pci_dev, Error **errp)
{VirtIOPCIProxy *proxy = VIRTIO_PCI(pci_dev);VirtioPCIClass *k = VIRTIO_PCI_GET_CLASS(pci_dev);bool pcie_port = pci_bus_is_express(pci_get_bus(pci_dev)) &&!pci_bus_is_root(pci_get_bus(pci_dev));if (kvm_enabled() && !kvm_has_many_ioeventfds()) {proxy->flags &= ~VIRTIO_PCI_FLAG_USE_IOEVENTFD;}/* fd-based ioevents can't be synchronized in record/replay */if (replay_mode != REPLAY_MODE_NONE) {proxy->flags &= ~VIRTIO_PCI_FLAG_USE_IOEVENTFD;}/** virtio pci bar layout used by default.* subclasses can re-arrange things if needed.**   region 0   --  virtio legacy io bar*   region 1   --  msi-x bar*   region 2   --  virtio modern io bar (off by default)*   region 4+5 --  virtio modern memory (64bit) bar**/proxy->legacy_io_bar_idx  = 0;proxy->msix_bar_idx       = 1;proxy->modern_io_bar_idx  = 2;proxy->modern_mem_bar_idx = 4;proxy->common.offset = 0x0;proxy->common.size = 0x1000;proxy->common.type = VIRTIO_PCI_CAP_COMMON_CFG;proxy->isr.offset = 0x1000;proxy->isr.size = 0x1000;proxy->isr.type = VIRTIO_PCI_CAP_ISR_CFG;proxy->device.offset = 0x2000;proxy->device.size = 0x1000;proxy->device.type = VIRTIO_PCI_CAP_DEVICE_CFG;proxy->notify.offset = 0x3000;proxy->notify.size = virtio_pci_queue_mem_mult(proxy) * VIRTIO_QUEUE_MAX;proxy->notify.type = VIRTIO_PCI_CAP_NOTIFY_CFG;proxy->notify_pio.offset = 0x0;proxy->notify_pio.size = 0x4;proxy->notify_pio.type = VIRTIO_PCI_CAP_NOTIFY_CFG;/* subclasses can enforce modern, so do this unconditionally */memory_region_init(&proxy->modern_bar, OBJECT(proxy), "virtio-pci",/* PCI BAR regions must be powers of 2 */pow2ceil(proxy->notify.offset + proxy->notify.size));if (proxy->disable_legacy == ON_OFF_AUTO_AUTO) {proxy->disable_legacy = pcie_port ? ON_OFF_AUTO_ON : ON_OFF_AUTO_OFF;}if (!virtio_pci_modern(proxy) && !virtio_pci_legacy(proxy)) {error_setg(errp, "device cannot work as neither modern nor legacy mode"" is enabled");error_append_hint(errp, "Set either disable-modern or disable-legacy"" to off\n");return;}if (pcie_port && pci_is_express(pci_dev)) {int pos;uint16_t last_pcie_cap_offset = PCI_CONFIG_SPACE_SIZE;pos = pcie_endpoint_cap_init(pci_dev, 0);assert(pos > 0);pos = pci_add_capability(pci_dev, PCI_CAP_ID_PM, 0,PCI_PM_SIZEOF, errp);if (pos < 0) {return;}pci_dev->exp.pm_cap = pos;/** Indicates that this function complies with revision 1.2 of the* PCI Power Management Interface Specification.*/pci_set_word(pci_dev->config + pos + PCI_PM_PMC, 0x3);if (proxy->flags & VIRTIO_PCI_FLAG_AER) {pcie_aer_init(pci_dev, PCI_ERR_VER, last_pcie_cap_offset,PCI_ERR_SIZEOF, NULL);last_pcie_cap_offset += PCI_ERR_SIZEOF;}if (proxy->flags & VIRTIO_PCI_FLAG_INIT_DEVERR) {/* Init error enabling flags */pcie_cap_deverr_init(pci_dev);}if (proxy->flags & VIRTIO_PCI_FLAG_INIT_LNKCTL) {/* Init Link Control Register */pcie_cap_lnkctl_init(pci_dev);}if (proxy->flags & VIRTIO_PCI_FLAG_INIT_PM) {/* Init Power Management Control Register */pci_set_word(pci_dev->wmask + pos + PCI_PM_CTRL,PCI_PM_CTRL_STATE_MASK);}if (proxy->flags & VIRTIO_PCI_FLAG_ATS) {pcie_ats_init(pci_dev, last_pcie_cap_offset,proxy->flags & VIRTIO_PCI_FLAG_ATS_PAGE_ALIGNED);last_pcie_cap_offset += PCI_EXT_CAP_ATS_SIZEOF;}if (proxy->flags & VIRTIO_PCI_FLAG_INIT_FLR) {/* Set Function Level Reset capability bit */pcie_cap_flr_init(pci_dev);}} else {/** make future invocations of pci_is_express() return false* and pci_config_size() return PCI_CONFIG_SPACE_SIZE.*/pci_dev->cap_present &= ~QEMU_PCI_CAP_EXPRESS;}virtio_pci_bus_new(&proxy->bus, sizeof(proxy->bus), proxy);if (k->realize) {k->realize(proxy, errp);}
}

在这个函数的最后会调用VirtioPCIClass的realize函数指针所指向的函数，也就是virtio_balloon_pci_realize函数。代码片段如下：

static void virtio_pci_realize(PCIDevice *pci_dev, Error **errp)
{VirtIOPCIProxy *proxy = VIRTIO_PCI(pci_dev);VirtioPCIClass *k = VIRTIO_PCI_GET_CLASS(pci_dev);……if (k->realize) {k->realize(proxy, errp);}
}

这篇关于QEMU源码全解析 —— virtio（8）的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！


http://www.chinasem.cn/article/498310。

相关文章

python常见环境管理工具超全解析

python常见环境管理工具超全解析

《python常见环境管理工具超全解析》在Python开发中,管理多个项目及其依赖项通常是一个挑战,下面：本文主要介绍python常见环境管理工具的相关资料,文中通过代码介绍的非常详细,需要的朋友... 目录1. conda2. pip3. uvuv 工具自动创建和管理环境的特点4. setup.py5.
阅读更多...
全面解析HTML5中Checkbox标签

全面解析HTML5中Checkbox标签

《全面解析HTML5中Checkbox标签》Checkbox是HTML5中非常重要的表单元素之一，通过合理使用其属性和样式自定义方法，可以为用户提供丰富多样的交互体验，这篇文章给大家介绍HTML5中C... 在html5中，Checkbox（复选框）是一种常用的表单元素，允许用户在一组选项中选择多个项目。本
阅读更多...
Python包管理工具核心指令uvx举例详细解析

Python包管理工具核心指令uvx举例详细解析

《Python包管理工具核心指令uvx举例详细解析》：本文主要介绍Python包管理工具核心指令uvx的相关资料,uvx是uv工具链中用于临时运行Python命令行工具的高效执行器,依托Rust实... 目录一、uvx 的定位与核心功能二、uvx 的典型应用场景三、uvx 与传统工具对比四、uvx 的技术实
阅读更多...
SpringBoot排查和解决JSON解析错误(400 Bad Request)的方法

SpringBoot排查和解决JSON解析错误(400 Bad Request)的方法

《SpringBoot排查和解决JSON解析错误(400BadRequest)的方法》在开发SpringBootRESTfulAPI时,客户端与服务端的数据交互通常使用JSON格式,然而,JSON... 目录问题背景1. 问题描述2. 错误分析解决方案1. 手动重新输入jsON2. 使用工具清理JSON3.
阅读更多...
Redis过期删除机制与内存淘汰策略的解析指南

Redis过期删除机制与内存淘汰策略的解析指南

《Redis过期删除机制与内存淘汰策略的解析指南》在使用Redis构建缓存系统时,很多开发者只设置了EXPIRE但却忽略了背后Redis的过期删除机制与内存淘汰策略,下面小编就来和大家详细介绍一下... 目录1、简述2、Redis http://www.chinasem.cn的过期删除策略（Key Expir
阅读更多...
Go学习记录之runtime包深入解析

Go学习记录之runtime包深入解析

《Go学习记录之runtime包深入解析》Go语言runtime包管理运行时环境,涵盖goroutine调度、内存分配、垃圾回收、类型信息等核心功能,：本文主要介绍Go学习记录之runtime包的... 目录前言：一、runtime包内容学习1、作用：① Goroutine和并发控制：② 垃圾回收：③ 栈和
阅读更多...
Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析

Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析

《Spring组件实例化扩展点之InstantiationAwareBeanPostProcessor使用场景解析》InstantiationAwareBeanPostProcessor是Spring... 目录一、什么是InstantiationAwareBeanPostProcessor？二、核心方法解
阅读更多...
深入解析 Java Future 类及代码示例

深入解析 Java Future 类及代码示例

《深入解析JavaFuture类及代码示例》JavaFuture是java.util.concurrent包中用于表示异步计算结果的核心接口,下面给大家介绍JavaFuture类及实例代码,感兴... 目录一、Future 类概述二、核心工作机制代码示例执行流程2. 状态机模型3. 核心方法解析行为总结：三
阅读更多...
springboot项目中使用JOSN解析库的方法

springboot项目中使用JOSN解析库的方法

《springboot项目中使用JOSN解析库的方法》JSON,全程是JavaScriptObjectNotation,是一种轻量级的数据交换格式,本文给大家介绍springboot项目中使用JOSN... 目录一、jsON解析简介二、Spring Boot项目中使用JSON解析1、pom.XML文件引入依
阅读更多...
Python中文件读取操作漏洞深度解析与防护指南

Python中文件读取操作漏洞深度解析与防护指南

《Python中文件读取操作漏洞深度解析与防护指南》在Web应用开发中,文件操作是最基础也最危险的功能之一,这篇文章将全面剖析Python环境中常见的文件读取漏洞类型,成因及防护方案,感兴趣的小伙伴可... 目录引言一、静态资源处理中的路径穿越漏洞1.1 典型漏洞场景1.2 os.path.join()的陷
阅读更多...

Copyright China编程 23002807@qq.com

沪ICP备2023033072号-2