pub fn run_gpu_device(opts: Options) -> anyhow::Result<()> {
let Options {
x_display,
params: mut gpu_parameters,
resource_bridge,
socket,
wayland_sock,
} = opts;
let channels: BTreeMap<_, _> = wayland_sock.in
to_iter().collect();
let resource_bridge_listeners = resource_bridge
.in
to_iter()
.map(|p| {
UnixSeqpacketListener::bind(&p)
.map(UnlinkUnixSeqpacketListener)
.with_context(|| format!("failed
to bind socket at path {}", p))
})
.collect::<anyhow::Result<Vec<_>>>()?;
if gpu_parameters.display_params.is_empty() {
gpu_parameters
.display_params
.push(GpuDisplayParameters::default());
}
let ex = Execu
tor::new().context("failed
to create execu
tor")?;
// We don't know the order in which other devices are going
to connect
to the resource bridges
// so start listening for all of them on separate threads. Any devices that connect after the
// gpu device starts its queues will not have its resource bridges processed. In practice this
// should
be fine since the devices that use the resource bridge always try
to connect
to the
// gpu device
before handling messages from the VM.
let resource_bridges = Arc::new(Mutex::new(Vec::with_capacity(
resource_bridge_listeners.len(),
)));
for listener in resource_bridge_listeners {
let resource_bridges = Arc::clone(&resource_bridges);
ex.spawn_blocking(move || match listener.accept() {
Ok(stream) => resource_bridges
.lock()
.push(Tu
be::new_from_unix_seqpacket(stream).unwrap()),
Err(e) => {
let path = listener
.path()
.unwrap_or_else(|_| PathBuf::from("{unknown}"));
error!(
"Failed
to accept resource bridge connection for socket {}: {}",
path.display(),
e
);
}
})
.detach();
}
//
TODO(b/232344535): Read side of the tu
be is ignored currently.
// Complete the implementation by polling `exit_evt_rdtu
be` and
// kill the sibling VM.
let (exit_evt_wrtu
be, _) =
Tu
be::directional_pair().context("failed
to create vm event tu
be")?;
let (gpu_control_tu
be, _) = Tu
be::pair().context("failed
to create gpu control tu
be")?;
let mut display_backends = vec![
virtio::DisplayBackend::X(x_display),
virtio::DisplayBackend::Stub,
];
if let
Some(p) = channels.get("") {
display_backends.insert(0, virtio::DisplayBackend::Wayland(
Some(p.
to_owned())));
}
// These are only used when there is an input device.
let event_devices = Vec::new();
let base_features = virtio::base_features(ProtectionType::Unprotected);
let listener = VhostUserListener::new_socket(&socket, None)?;
let gpu = Rc::new(RefCell::new(Gpu::new(
exit_evt_wrtu
be,
gpu_control_tu
be,
Vec::new(), // resource_bridges, handled separately by us
display_backends,
&gpu_parameters,
/* rutabaga_server_descrip
tor */
None,
event_devices,
base_features,
&channels,
/* gpu_cgroup_path */
None,
)));
let backend = GpuBackend {
ex: ex.clone(),
gpu,
resource_bridges,
state: None,
fence_state: Default::default(),
queue_workers: Default::default(),
platform_workers: Default::default(),
shmem_mapper: Arc::new(Mutex::new(None)),
};
// Run until the backend is
finished.
let _ = ex.run_until(listener.run_backend(backend, &ex))?;
// Process any
tasks from the backend's destruc
tor.
Ok(ex.run_until(async {})?)
}
本文涵盖Windows编程核心技能的学习与实践，包括阅读《Programming Windows》理解消息路由及窗口绘制，深入研究MFC框架，实现托盘程序。此外，还涉及经典游戏如俄罗斯方块和扫雷的开发过程，强调遵循编码规范，并探讨了红蓝设计模式的实现方法。
扫一扫
1829
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
