Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openeuler
Kernel
提交
b3e28b65
K
Kernel
项目概览
openeuler
/
Kernel
1 年多 前同步成功
通知
8
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
K
Kernel
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
提交
b3e28b65
编写于
2月 11, 2015
作者:
R
Rusty Russell
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
lguest: remove lguest bus definitions from header.
Signed-off-by:
N
Rusty Russell
<
rusty@rustcorp.com.au
>
上级
d9028eda
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
2 addition
and
47 deletion
+2
-47
include/linux/lguest_launcher.h
include/linux/lguest_launcher.h
+2
-47
未找到文件。
include/linux/lguest_launcher.h
浏览文件 @
b3e28b65
...
...
@@ -8,52 +8,13 @@
*
* The Guest needs devices to do anything useful. Since we don't let it touch
* real devices (think of the damage it could do!) we provide virtual devices.
* We could emulate a PCI bus with various devices on it, but that is a fairly
* complex burden for the Host and suboptimal for the Guest, so we have our own
* simple lguest bus and we use "virtio" drivers. These drivers need a set of
* routines from us which will actually do the virtual I/O, but they handle all
* the net/block/console stuff themselves. This means that if we want to add
* a new device, we simply need to write a new virtio driver and create support
* for it in the Launcher: this code won't need to change.
* We emulate a PCI bus with virtio devices on it; we used to have our own
* lguest bus which was far simpler, but this tests the virtio 1.0 standard.
*
* Virtio devices are also used by kvm, so we can simply reuse their optimized
* device drivers. And one day when everyone uses virtio, my plan will be
* complete. Bwahahahah!
*
* Devices are described by a simplified ID, a status byte, and some "config"
* bytes which describe this device's configuration. This is placed by the
* Launcher just above the top of physical memory:
*/
struct
lguest_device_desc
{
/* The device type: console, network, disk etc. Type 0 terminates. */
__u8
type
;
/* The number of virtqueues (first in config array) */
__u8
num_vq
;
/*
* The number of bytes of feature bits. Multiply by 2: one for host
* features and one for Guest acknowledgements.
*/
__u8
feature_len
;
/* The number of bytes of the config array after virtqueues. */
__u8
config_len
;
/* A status byte, written by the Guest. */
__u8
status
;
__u8
config
[
0
];
};
/*D:135
* This is how we expect the device configuration field for a virtqueue
* to be laid out in config space.
*/
struct
lguest_vqconfig
{
/* The number of entries in the virtio_ring */
__u16
num
;
/* The interrupt we get when something happens. */
__u16
irq
;
/* The page number of the virtio ring for this device. */
__u32
pfn
;
};
/*:*/
/* Write command first word is a request. */
enum
lguest_req
...
...
@@ -80,10 +41,4 @@ struct lguest_pending {
__u8
insn
[
7
];
__u32
addr
;
};
/*
* The alignment to use between consumer and producer parts of vring.
* x86 pagesize for historical reasons.
*/
#define LGUEST_VRING_ALIGN 4096
#endif
/* _LINUX_LGUEST_LAUNCHER */
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录