On Fri, Apr 12, 2024 at 02:57:00PM +0800, Yi-De Wu wrote: > From: "Yingshiuan Pan" <yingshiuan.pan@xxxxxxxxxxxx> > > Add documentation for GenieZone(gzvm) node. This node informs gzvm > driver to start probing if geniezone hypervisor is available and > able to do virtual machine operations. > > [Reason to use dt solution] > - The GenieZone hypervisor serves as a vendor model for facilitating > platform virtualization, with an implementation that is independent > from Linuxism. > - In contrast to the dt solution, our previous approach involved probing > via hypercall to determine the existence of our hypervisor. However, this > method raised concerns about potentially impacting all systems, including > those without the GenieZone hypervisor embedded[ref]. > > Link: https://lore.kernel.org/all/2fe0c7f9-55fc-ae63-3631-8526a0212ccd@xxxxxxxxxx/ > +properties: > + compatible: > + const: mediatek,geniezone-hyp Been avoiding this binding every time it shows up because Rob had already told you no and hasn't revisited it since, but I feel this should be s/-hyp// since that's redundant information. > +description: > + This interface is designed for integrating GenieZone hypervisor into Android > + Virtualization Framework(AVF) along with Crosvm as a VMM. > + It acts like a wrapper for every hypercall to GenieZone hypervisor in > + order to control guest VM lifecycles and virtual interrupt injections. The description however doesn't really make sense. The binding claims to be for geniezone but the description talks about something else entirely that "acts like a wrapper" between the OS and geniezone. What is the binding actually for?
Attachment:
signature.asc
Description: PGP signature
