From: Elliot Berman <quic_eberman@quicinc.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Bjorn Andersson <quic_bjorande@quicinc.com>, Alex Elder <elder@linaro.org>, Murali Nalajala <quic_mnalajal@quicinc.com>, Jonathan Corbet <corbet@lwn.net> Cc: Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Arnd Bergmann <arnd@arndb.de>, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Bagas Sanjaya <bagasdotme@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, "Will Deacon" <will@kernel.org>, Marc Zyngier <maz@kernel.org>, Jassi Brar <jassisinghbrar@gmail.com>, Sudeep Holla <sudeep.holla@arm.com>, <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v9 21/27] gunyah: vm_mgr: Add framework to add VM Functions Date: Wed, 8 Feb 2023 11:34:10 -0800 [thread overview] Message-ID: <f48868a9-313d-b3ee-d8b2-98774f0d1cd8@quicinc.com> (raw) In-Reply-To: <c1564a80-d1be-f31d-2db3-1ec0b847e921@linaro.org> On 2/7/2023 5:15 AM, Srinivas Kandagatla wrote: > > > On 20/01/2023 22:46, Elliot Berman wrote: >> Introduce a framework for Gunyah userspace to install VM functions. VM >> functions are optional interfaces to the virtual machine. vCPUs, >> ioeventfs, and irqfds are examples of such VM functions and are >> implemented in subsequent patches. >> >> A generic framework is implemented instead of individual ioctls to >> create vCPUs, irqfds, etc., in order to simplify the VM manager core >> implementation and allow dynamic loading of VM function modules. >> >> Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> >> --- [snip] >> +#define DECLARE_GUNYAH_VM_FUNCTION(_name, _bind, _release) \ >> + static struct gunyah_vm_function_driver _name = { \ >> + .name = __stringify(_name), \ >> + .mod = THIS_MODULE, \ >> + .bind = _bind, \ >> + .release = _release, \ >> + }; \ >> + MODULE_ALIAS("ghfunc:"__stringify(_name)) > > lets not over kill this by having DECLARE_GUNYAH_VM_FUNCTION, this will > make the drivers readable in a more familar way. let the driver define > this static struct. > > >> + >> +#define DECLARE_GUNYAH_VM_FUNCTION_INIT(_name, _bind, _release) \ >> + DECLARE_GUNYAH_VM_FUNCTION(_name, _bind, _release); \ >> + static int __init _name##_mod_init(void) \ >> + { \ >> + return gunyah_vm_function_register(&(_name)); \ >> + } \ >> + module_init(_name##_mod_init); \ >> + static void __exit _name##_mod_exit(void) \ >> + { \ >> + gunyah_vm_function_unregister(&(_name)); \ >> + } \ >> + module_exit(_name##_mod_exit) >> + > > How about: > > #define module_gunyah_function_driver(__gf_driver) > module_driver(__gf_driver, gunyah_vm_function_register, \ > gunyah_vm_function_unregister) > > Having relook at the patch, I think modeling the gunyah_vm_function as a > proper device and driver model will scale, you could leverage most of > this manual management to the existing driver model. May I suggest to > you take a look at include/linux/auxiliary_bus.h > with that you could model add_functions as > auxiliary_device_add and the respecitive drivers as > module_auxiliary_driver. > I'm not sure if device model can fit well here. I wanted to make sure that the VM function actually bound to a driver when user requests it and the driver to be able to return some info about it to the user -- vCPUs return a file descriptor for instance. I could probably make it work with a device/driver model, but I'm not sure if it should be done like that. >> +#endif >> diff --git a/include/uapi/linux/gunyah.h b/include/uapi/linux/gunyah.h >> index 36359ad2175e..ec8da6fde045 100644 >> --- a/include/uapi/linux/gunyah.h >> +++ b/include/uapi/linux/gunyah.h >> @@ -50,4 +50,17 @@ struct gh_vm_dtb_config { >> #define GH_VM_START _IO(GH_IOCTL_TYPE, 0x3) >> +#define GUNYAH_FUNCTION_NAME_SIZE 32 >> +#define GUNYAH_FUNCTION_MAX_ARG_SIZE 1024 >> + >> +struct gh_vm_function { >> + char name[GUNYAH_FUNCTION_NAME_SIZE]; >> + union { >> + char data[GUNYAH_FUNCTION_MAX_ARG_SIZE]; > > Are we missing any thing here, its odd to see a single member union like > this. > if other memembers are part of another patch please move them to this > one as its confusing. I can add a comment that members will be added as new functions are added. If I put it in this patch, it raises questions about where those other members are being used.
WARNING: multiple messages have this Message-ID (diff)
From: Elliot Berman <quic_eberman@quicinc.com> To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Bjorn Andersson <quic_bjorande@quicinc.com>, Alex Elder <elder@linaro.org>, Murali Nalajala <quic_mnalajal@quicinc.com>, Jonathan Corbet <corbet@lwn.net> Cc: Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Arnd Bergmann <arnd@arndb.de>, "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Bagas Sanjaya <bagasdotme@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, "Will Deacon" <will@kernel.org>, Marc Zyngier <maz@kernel.org>, Jassi Brar <jassisinghbrar@gmail.com>, Sudeep Holla <sudeep.holla@arm.com>, <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [PATCH v9 21/27] gunyah: vm_mgr: Add framework to add VM Functions Date: Wed, 8 Feb 2023 11:34:10 -0800 [thread overview] Message-ID: <f48868a9-313d-b3ee-d8b2-98774f0d1cd8@quicinc.com> (raw) In-Reply-To: <c1564a80-d1be-f31d-2db3-1ec0b847e921@linaro.org> On 2/7/2023 5:15 AM, Srinivas Kandagatla wrote: > > > On 20/01/2023 22:46, Elliot Berman wrote: >> Introduce a framework for Gunyah userspace to install VM functions. VM >> functions are optional interfaces to the virtual machine. vCPUs, >> ioeventfs, and irqfds are examples of such VM functions and are >> implemented in subsequent patches. >> >> A generic framework is implemented instead of individual ioctls to >> create vCPUs, irqfds, etc., in order to simplify the VM manager core >> implementation and allow dynamic loading of VM function modules. >> >> Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> >> --- [snip] >> +#define DECLARE_GUNYAH_VM_FUNCTION(_name, _bind, _release) \ >> + static struct gunyah_vm_function_driver _name = { \ >> + .name = __stringify(_name), \ >> + .mod = THIS_MODULE, \ >> + .bind = _bind, \ >> + .release = _release, \ >> + }; \ >> + MODULE_ALIAS("ghfunc:"__stringify(_name)) > > lets not over kill this by having DECLARE_GUNYAH_VM_FUNCTION, this will > make the drivers readable in a more familar way. let the driver define > this static struct. > > >> + >> +#define DECLARE_GUNYAH_VM_FUNCTION_INIT(_name, _bind, _release) \ >> + DECLARE_GUNYAH_VM_FUNCTION(_name, _bind, _release); \ >> + static int __init _name##_mod_init(void) \ >> + { \ >> + return gunyah_vm_function_register(&(_name)); \ >> + } \ >> + module_init(_name##_mod_init); \ >> + static void __exit _name##_mod_exit(void) \ >> + { \ >> + gunyah_vm_function_unregister(&(_name)); \ >> + } \ >> + module_exit(_name##_mod_exit) >> + > > How about: > > #define module_gunyah_function_driver(__gf_driver) > module_driver(__gf_driver, gunyah_vm_function_register, \ > gunyah_vm_function_unregister) > > Having relook at the patch, I think modeling the gunyah_vm_function as a > proper device and driver model will scale, you could leverage most of > this manual management to the existing driver model. May I suggest to > you take a look at include/linux/auxiliary_bus.h > with that you could model add_functions as > auxiliary_device_add and the respecitive drivers as > module_auxiliary_driver. > I'm not sure if device model can fit well here. I wanted to make sure that the VM function actually bound to a driver when user requests it and the driver to be able to return some info about it to the user -- vCPUs return a file descriptor for instance. I could probably make it work with a device/driver model, but I'm not sure if it should be done like that. >> +#endif >> diff --git a/include/uapi/linux/gunyah.h b/include/uapi/linux/gunyah.h >> index 36359ad2175e..ec8da6fde045 100644 >> --- a/include/uapi/linux/gunyah.h >> +++ b/include/uapi/linux/gunyah.h >> @@ -50,4 +50,17 @@ struct gh_vm_dtb_config { >> #define GH_VM_START _IO(GH_IOCTL_TYPE, 0x3) >> +#define GUNYAH_FUNCTION_NAME_SIZE 32 >> +#define GUNYAH_FUNCTION_MAX_ARG_SIZE 1024 >> + >> +struct gh_vm_function { >> + char name[GUNYAH_FUNCTION_NAME_SIZE]; >> + union { >> + char data[GUNYAH_FUNCTION_MAX_ARG_SIZE]; > > Are we missing any thing here, its odd to see a single member union like > this. > if other memembers are part of another patch please move them to this > one as its confusing. I can add a comment that members will be added as new functions are added. If I put it in this patch, it raises questions about where those other members are being used. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-08 19:34 UTC|newest] Thread overview: 154+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-20 22:45 [PATCH v9 00/27] Drivers for gunyah hypervisor Elliot Berman 2023-01-20 22:45 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 01/27] docs: gunyah: Introduce Gunyah Hypervisor Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 02/27] dt-bindings: Add binding for gunyah hypervisor Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 03/27] gunyah: Common types and error codes for Gunyah hypercalls Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-30 9:58 ` Greg Kroah-Hartman 2023-01-30 9:58 ` Greg Kroah-Hartman 2023-01-20 22:46 ` [PATCH v9 04/27] virt: gunyah: Add hypercalls to identify Gunyah Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-30 10:01 ` Greg Kroah-Hartman 2023-01-30 10:01 ` Greg Kroah-Hartman 2023-01-30 19:05 ` Elliot Berman 2023-01-30 19:05 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 05/27] virt: gunyah: Identify hypervisor version Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 06/27] mailbox: Allow direct registration to a channel Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 07/27] virt: gunyah: msgq: Add hypercalls to send and receive messages Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-31 16:16 ` Srinivas Kandagatla 2023-01-31 16:16 ` Srinivas Kandagatla 2023-01-20 22:46 ` [PATCH v9 08/27] mailbox: Add Gunyah message queue mailbox Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-02 9:59 ` Srinivas Kandagatla 2023-02-02 9:59 ` Srinivas Kandagatla 2023-02-06 14:00 ` Alex Elder 2023-02-06 14:00 ` Alex Elder 2023-02-08 20:46 ` Elliot Berman 2023-02-08 20:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 09/27] gunyah: rsc_mgr: Add resource manager RPC core Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-02 11:53 ` Srinivas Kandagatla 2023-02-02 11:53 ` Srinivas Kandagatla 2023-02-06 14:14 ` Alex Elder 2023-02-06 14:14 ` Alex Elder 2023-01-20 22:46 ` [PATCH v9 10/27] gunyah: rsc_mgr: Add VM lifecycle RPC Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-25 6:12 ` Srivatsa Vaddagiri 2023-01-25 6:12 ` Srivatsa Vaddagiri 2023-01-30 21:43 ` Elliot Berman 2023-01-30 21:43 ` Elliot Berman 2023-02-02 12:46 ` Srinivas Kandagatla 2023-02-02 12:46 ` Srinivas Kandagatla 2023-02-06 15:41 ` Alex Elder 2023-02-06 15:41 ` Alex Elder 2023-02-06 17:38 ` Elliot Berman 2023-02-06 17:38 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 11/27] gunyah: vm_mgr: Introduce basic VM Manager Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-02 12:54 ` Srinivas Kandagatla 2023-02-02 12:54 ` Srinivas Kandagatla 2023-02-07 0:36 ` Elliot Berman 2023-02-07 0:36 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 12/27] gunyah: rsc_mgr: Add RPC for sharing memory Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-30 10:14 ` Srivatsa Vaddagiri 2023-01-30 10:14 ` Srivatsa Vaddagiri 2023-01-30 21:45 ` Elliot Berman 2023-01-30 21:45 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 13/27] gunyah: vm_mgr: Add/remove user memory regions Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-25 13:34 ` Srivatsa Vaddagiri 2023-01-25 13:34 ` Srivatsa Vaddagiri 2023-01-30 21:46 ` Elliot Berman 2023-01-30 21:46 ` Elliot Berman 2023-02-06 16:12 ` Srinivas Kandagatla 2023-02-06 16:12 ` Srinivas Kandagatla 2023-02-06 23:23 ` Elliot Berman 2023-02-06 23:23 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 14/27] gunyah: vm_mgr: Add ioctls to support basic non-proxy VM boot Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-30 8:53 ` Srivatsa Vaddagiri 2023-01-30 8:53 ` Srivatsa Vaddagiri 2023-01-30 21:44 ` Elliot Berman 2023-01-30 21:44 ` Elliot Berman 2023-01-30 21:45 ` Elliot Berman 2023-01-30 21:45 ` Elliot Berman 2023-02-07 11:36 ` Srinivas Kandagatla 2023-02-07 11:36 ` Srinivas Kandagatla 2023-02-08 21:04 ` Elliot Berman 2023-02-08 21:04 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 15/27] samples: Add sample userspace Gunyah VM Manager Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 16/27] gunyah: rsc_mgr: Add platform ops on mem_lend/mem_reclaim Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 17/27] firmware: qcom_scm: Use fixed width src vm bitmap Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-03-16 3:21 ` (subset) " Bjorn Andersson 2023-03-16 3:21 ` Bjorn Andersson 2023-03-16 3:21 ` Bjorn Andersson 2023-01-20 22:46 ` [PATCH v9 18/27] firmware: qcom_scm: Register Gunyah platform ops Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-31 15:18 ` Srivatsa Vaddagiri 2023-01-31 15:18 ` Srivatsa Vaddagiri 2023-02-07 11:52 ` Srinivas Kandagatla 2023-02-07 11:52 ` Srinivas Kandagatla 2023-02-08 1:06 ` Elliot Berman 2023-02-08 1:06 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 19/27] docs: gunyah: Document Gunyah VM Manager Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 20/27] virt: gunyah: Translate gh_rm_hyp_resource into gunyah_resource Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 21/27] gunyah: vm_mgr: Add framework to add VM Functions Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-03 9:37 ` Srivatsa Vaddagiri 2023-02-03 9:37 ` Srivatsa Vaddagiri 2023-02-03 17:56 ` Srivatsa Vaddagiri 2023-02-03 17:56 ` Srivatsa Vaddagiri 2023-02-07 13:15 ` Srinivas Kandagatla 2023-02-07 13:15 ` Srinivas Kandagatla 2023-02-08 19:34 ` Elliot Berman [this message] 2023-02-08 19:34 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 22/27] virt: gunyah: Add resource tickets Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-06 9:50 ` Srivatsa Vaddagiri 2023-02-06 9:50 ` Srivatsa Vaddagiri 2023-02-06 21:30 ` Elliot Berman 2023-02-06 21:30 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 23/27] virt: gunyah: Add IO handlers Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-06 10:46 ` Srivatsa Vaddagiri 2023-02-06 10:46 ` Srivatsa Vaddagiri 2023-02-07 3:59 ` Elliot Berman 2023-02-07 3:59 ` Elliot Berman 2023-02-07 12:19 ` Srivatsa Vaddagiri 2023-02-07 12:19 ` Srivatsa Vaddagiri 2023-01-20 22:46 ` [PATCH v9 24/27] virt: gunyah: Add proxy-scheduled vCPUs Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-07 14:43 ` Srinivas Kandagatla 2023-02-07 14:43 ` Srinivas Kandagatla 2023-02-08 18:36 ` Elliot Berman 2023-02-08 18:36 ` Elliot Berman 2023-02-09 10:39 ` Srivatsa Vaddagiri 2023-02-09 10:39 ` Srivatsa Vaddagiri 2023-02-10 6:54 ` Srivatsa Vaddagiri 2023-02-10 6:54 ` Srivatsa Vaddagiri 2023-02-10 17:09 ` Elliot Berman 2023-02-10 17:09 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 25/27] virt: gunyah: Add hypercalls for sending doorbell Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-01-20 22:46 ` [PATCH v9 26/27] virt: gunyah: Add irqfd interface Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-07 14:30 ` Srinivas Kandagatla 2023-02-07 14:30 ` Srinivas Kandagatla 2023-02-13 8:11 ` Srivatsa Vaddagiri 2023-02-13 8:11 ` Srivatsa Vaddagiri 2023-01-20 22:46 ` [PATCH v9 27/27] virt: gunyah: Add ioeventfd Elliot Berman 2023-01-20 22:46 ` Elliot Berman 2023-02-07 14:19 ` Srinivas Kandagatla 2023-02-07 14:19 ` Srinivas Kandagatla
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=f48868a9-313d-b3ee-d8b2-98774f0d1cd8@quicinc.com \ --to=quic_eberman@quicinc.com \ --cc=arnd@arndb.de \ --cc=bagasdotme@gmail.com \ --cc=catalin.marinas@arm.com \ --cc=corbet@lwn.net \ --cc=devicetree@vger.kernel.org \ --cc=dmitry.baryshkov@linaro.org \ --cc=elder@linaro.org \ --cc=gregkh@linuxfoundation.org \ --cc=jassisinghbrar@gmail.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=maz@kernel.org \ --cc=quic_bjorande@quicinc.com \ --cc=quic_cvanscha@quicinc.com \ --cc=quic_mnalajal@quicinc.com \ --cc=quic_pheragu@quicinc.com \ --cc=quic_svaddagi@quicinc.com \ --cc=quic_tsoni@quicinc.com \ --cc=robh+dt@kernel.org \ --cc=srinivas.kandagatla@linaro.org \ --cc=sudeep.holla@arm.com \ --cc=will@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.