-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generalize GUI daemon's xc_map_foreign_pages() #2619
Comments
While touching the GUID and reworking the xc_map_forgein_pages() for work with GUI domain, we should also make an effort to generalize this call to allow for future architectures not based on Xen. Ideally not even based on shared-memory-based hardware architectures. Here the primary observation is that our GUI protocol already comprises two channels:
So, the generalized version of the protocol should allow for providing independent implementations of this data channel (e.g. over network). |
Can you use full "GUI daemon" name? GUID means "globally unique identifier". |
For the record, this is implemented in: |
GUI agent now links directly with libxengnttab. QubesOS/qubes-issues#2619
This version will not work with qubes-gui-agent not supporting -d option. QubesOS/qubes-issues#2619
@marmarek can this be closed since QubesOS/qubes-gui-agent-xen-hvm-stubdom@e341ebd? |
In theory there is one more component needed to be ported - gui-agent-windows. But it's kind of unmaintained... |
A few changes will be needed to allow to run gui-daemon in non-Dom0 VM when used in "true GuiDom" mode.
Some of these changes (especially with regards connection establishing between other AppVMs and GuiDom) should be resolved as part of #833. However, completing of #833 will likely not solve the problem with guid relying on the Xen's
xc_map_foreign_pages
(see https://github.com/QubesOS/qubes-gui-daemon/blob/v3.2.8/shmoverride/shmoverride.c#L76), which we need to solve for use with true GuiDom implementation.The text was updated successfully, but these errors were encountered: