You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[mtijanic] Please use this issue to ask simple questions about the codebase, such as what a certain feature is, how a given codepath works, what a given acronym means, etc. Please keep your questions as specific as possible.
-- Original user post below this line --
I see a lot of RM in the code related to the RMAPI module, what does this RM and GSP-RM mean exactly?
RM stands for "Resource Manager" and it is the internal name of the driver that gets compiled into nvidia.ko module - both the open source one (sometimes referred to as "OpenRM" internally) and the proprietary version. It can also refer to the team working on this code.
Depending on the context, GSP-RM can refer either to the new driver architecture that uses the "GSP" microcontroller, or it can refer to the code running on said microcontroller. To avoid ambiguity, the latter is often called "Physical RM" instead, and code running in kernel is called "Kernel RM".
RMAPI is the interface nvidia.ko (RM) exposes to other kernel modules and to userspace.
@antdking Please see #44 . I do agree Discussions would be a much cleaner option, and I expect we'll enable them soon enough. Will gladly retire this issue when that happens, but until such a time this is the best we have for these quick one-off questions.
Will this driver support GPU virtualization with untrusted guests on consumer hardware? This would be a huge win for Qubes OS, which is currently forced to rely on software rendering. Support for CUDA or for enterprise GPUs would not be as helpful, as Qubes OS is an end-user operating system focused on the desktop use-case.
@DemiMarie At this point all I can say is that the current codebase does not support virtualization - neither as a host nor a guest. I don't currently have any information about future changes in this regard.
Activity
mtijanic commentedon May 13, 2022
Hello and thank you for your interest!
RM stands for "Resource Manager" and it is the internal name of the driver that gets compiled into
nvidia.komodule - both the open source one (sometimes referred to as "OpenRM" internally) and the proprietary version. It can also refer to the team working on this code.Depending on the context, GSP-RM can refer either to the new driver architecture that uses the "GSP" microcontroller, or it can refer to the code running on said microcontroller. To avoid ambiguity, the latter is often called "Physical RM" instead, and code running in kernel is called "Kernel RM".
RMAPI is the interface nvidia.ko (RM) exposes to other kernel modules and to userspace.
mtijanic commentedon May 13, 2022
Meta: Do you think it makes sense to group these questions into a single issue, which we could then pin?
s66104444 commentedon May 13, 2022
Thanks! Yes, I think it's a good idea to group these questions into a single issue.
[-]RM[/-][+]Ask questions about the codebase here[/+]mtijanic commentedon May 13, 2022
Okay, this is now a pinned generic code-related Q&A issue.
antdking commentedon May 13, 2022
Would it be possible to enable Github Discussions, which has a cleaner structure for quick questions?
mtijanic commentedon May 13, 2022
@antdking Please see #44 . I do agree Discussions would be a much cleaner option, and I expect we'll enable them soon enough. Will gladly retire this issue when that happens, but until such a time this is the best we have for these quick one-off questions.
DemiMarie commentedon May 13, 2022
Will this driver support GPU virtualization with untrusted guests on consumer hardware? This would be a huge win for Qubes OS, which is currently forced to rely on software rendering. Support for CUDA or for enterprise GPUs would not be as helpful, as Qubes OS is an end-user operating system focused on the desktop use-case.
mtijanic commentedon May 13, 2022
@DemiMarie At this point all I can say is that the current codebase does not support virtualization - neither as a host nor a guest. I don't currently have any information about future changes in this regard.