From: Alex Elder <elder@linaro.org> To: Elliot Berman <quic_eberman@quicinc.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>, Jonathan Corbet <corbet@lwn.net> Cc: Murali Nalajala <quic_mnalajal@quicinc.com>, Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@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>, Will Deacon <will@kernel.org>, Andy Gross <agross@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Jassi Brar <jassisinghbrar@gmail.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 v11 25/26] virt: gunyah: Add ioeventfd Date: Fri, 31 Mar 2023 09:27:46 -0500 [thread overview] Message-ID: <88a35ed3-78f9-c8ad-93b0-c7335e39a754@linaro.org> (raw) In-Reply-To: <20230304010632.2127470-26-quic_eberman@quicinc.com> On 3/3/23 7:06 PM, Elliot Berman wrote: > Allow userspace to attach an ioeventfd to an mmio address within the guest. > > Co-developed-by: Prakruthi Deepak Heragu <quic_pheragu@quicinc.com> > Signed-off-by: Prakruthi Deepak Heragu <quic_pheragu@quicinc.com> > Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> Mostly minor suggestions here. -Alex > --- > Documentation/virt/gunyah/vm-manager.rst | 2 +- > drivers/virt/gunyah/Kconfig | 9 ++ > drivers/virt/gunyah/Makefile | 1 + > drivers/virt/gunyah/gunyah_ioeventfd.c | 117 +++++++++++++++++++++++ > include/uapi/linux/gunyah.h | 37 +++++++ > 5 files changed, 165 insertions(+), 1 deletion(-) > create mode 100644 drivers/virt/gunyah/gunyah_ioeventfd.c > > diff --git a/Documentation/virt/gunyah/vm-manager.rst b/Documentation/virt/gunyah/vm-manager.rst > index a1dd70f0cbf6..cd41a705849f 100644 > --- a/Documentation/virt/gunyah/vm-manager.rst > +++ b/Documentation/virt/gunyah/vm-manager.rst > @@ -124,7 +124,7 @@ the VM starts. > The possible types are documented below: > > .. kernel-doc:: include/uapi/linux/gunyah.h > - :identifiers: GH_FN_VCPU gh_fn_vcpu_arg GH_FN_IRQFD gh_fn_irqfd_arg > + :identifiers: GH_FN_VCPU gh_fn_vcpu_arg GH_FN_IRQFD gh_fn_irqfd_arg GH_FN_IOEVENTFD gh_fn_ioeventfd_arg > > Gunyah VCPU API Descriptions > ---------------------------- > diff --git a/drivers/virt/gunyah/Kconfig b/drivers/virt/gunyah/Kconfig > index 2cde24d429d1..bd8e31184962 100644 > --- a/drivers/virt/gunyah/Kconfig > +++ b/drivers/virt/gunyah/Kconfig > @@ -35,3 +35,12 @@ config GUNYAH_IRQFD > on Gunyah virtual machine. > > Say Y/M here if unsure and you want to support Gunyah VMMs. > + > +config GUNYAH_IOEVENTFD > + tristate "Gunyah ioeventfd interface" > + depends on GUNYAH > + help > + Enable kernel support for creating ioeventfds which can alert userspace > + when a Gunyah virtual machine accesses a memory address. > + > + Say Y/M here if unsure and you want to support Gunyah VMMs. > diff --git a/drivers/virt/gunyah/Makefile b/drivers/virt/gunyah/Makefile > index 6cf756bfa3c2..7347b1470491 100644 > --- a/drivers/virt/gunyah/Makefile > +++ b/drivers/virt/gunyah/Makefile > @@ -8,3 +8,4 @@ obj-$(CONFIG_GUNYAH) += gunyah_rsc_mgr.o > > obj-$(CONFIG_GUNYAH_VCPU) += gunyah_vcpu.o > obj-$(CONFIG_GUNYAH_IRQFD) += gunyah_irqfd.o > +obj-$(CONFIG_GUNYAH_IOEVENTFD) += gunyah_ioeventfd.o > diff --git a/drivers/virt/gunyah/gunyah_ioeventfd.c b/drivers/virt/gunyah/gunyah_ioeventfd.c > new file mode 100644 > index 000000000000..517f55706ed9 > --- /dev/null > +++ b/drivers/virt/gunyah/gunyah_ioeventfd.c > @@ -0,0 +1,117 @@ > +// SPDX-License-Identifier: GPL-2.0-only > +/* > + * Copyright (c) 2022-2023 Qualcomm Innovation Center, Inc. All rights reserved. > + */ > + > +#include <linux/eventfd.h> > +#include <linux/file.h> > +#include <linux/fs.h> > +#include <linux/gunyah.h> > +#include <linux/gunyah_vm_mgr.h> > +#include <linux/module.h> > +#include <linux/printk.h> > + > +#include <uapi/linux/gunyah.h> > + > +struct gh_ioeventfd { > + struct gh_vm_function_instance *f; > + struct gh_vm_io_handler io_handler; > + > + struct eventfd_ctx *ctx; > +}; > + > +static int gh_write_ioeventfd(struct gh_vm_io_handler *io_dev, u64 addr, u32 len, u64 data) > +{ > + struct gh_ioeventfd *iofd = container_of(io_dev, struct gh_ioeventfd, io_handler); > + I think it's interesting that this signals an event even if len is zero. I'm not saying it's wrong, just interesting... > + eventfd_signal(iofd->ctx, 1); > + return 0; > +} > + > +static struct gh_vm_io_handler_ops io_ops = { > + .write = gh_write_ioeventfd, > +}; > + > +static long gh_ioeventfd_bind(struct gh_vm_function_instance *f) > +{ > + const struct gh_fn_ioeventfd_arg *args = f->argp; > + struct eventfd_ctx *ctx = NULL; No need to initialize ctx. > + struct gh_ioeventfd *iofd; > + int ret; > + > + if (f->arg_size != sizeof(*args)) > + return -EINVAL; > + > + /* must be natural-word sized, or 0 to ignore length */ > + switch (args->len) { > + case 0: > + case 1: > + case 2: > + case 4: > + case 8: > + break; > + default: > + return -EINVAL; > + } > + > + /* check for range overflow */ > + if (args->addr + args->len < args->addr) I think you could use: if (overflows_type(args->addr + args->len, args->addr)) This is a relatively recent addition (and I haven't been using it myself yet) but it's meant for this purpose. Consider using it and its relatives here and anywhere else you're making this kind of check. > + return -EINVAL; > + > + /* ioeventfd with no length can't be combined with DATAMATCH */ > + if (!args->len && (args->flags & GH_IOEVENTFD_DATAMATCH)) > + return -EINVAL; > + Maybe check for invalid flags before before ensuring valid flags are used properly? > + /* All other flag bits are reserved for future use */ > + if (args->flags & ~GH_IOEVENTFD_DATAMATCH) > + return -EINVAL; > + > + ctx = eventfd_ctx_fdget(args->fd); > + if (IS_ERR(ctx)) > + return PTR_ERR(ctx); > + > + iofd = kzalloc(sizeof(*iofd), GFP_KERNEL); > + if (!iofd) { > + ret = -ENOMEM; > + goto err_eventfd; > + } > + > + f->data = iofd; > + iofd->f = f; > + > + iofd->ctx = ctx; > + > + if (args->flags & GH_IOEVENTFD_DATAMATCH) { > + iofd->io_handler.datamatch = true; > + iofd->io_handler.len = args->len; > + iofd->io_handler.data = args->datamatch; I think you might want to rename one or the other of these fields (datamatch or data). I might be wrong; I'll explain elsewhere what I mean. > + } > + iofd->io_handler.addr = args->addr; > + iofd->io_handler.ops = &io_ops; > + > + ret = gh_vm_add_io_handler(f->ghvm, &iofd->io_handler); > + if (ret) > + goto err_io_dev_add; > + > + return 0; > + > +err_io_dev_add: > + kfree(iofd); > +err_eventfd: > + eventfd_ctx_put(ctx); > + return ret; > +} > + > +static void gh_ioevent_unbind(struct gh_vm_function_instance *f) > +{ > + struct gh_ioeventfd *iofd = f->data; > + > + eventfd_ctx_put(iofd->ctx); It's not a big deal but I prefer to "undo" everything in the reverse order that they are originally "done". I.e., put the eventfd context after removing the I/O handler. > + gh_vm_remove_io_handler(iofd->f->ghvm, &iofd->io_handler); > + kfree(iofd); > +} > + > +DECLARE_GH_VM_FUNCTION_INIT(ioeventfd, GH_FN_IOEVENTFD, > + gh_ioeventfd_bind, gh_ioevent_unbind); > +MODULE_DESCRIPTION("Gunyah ioeventfds"); s/ioeventfds/ioeventfd/ I understand why you might want it to be plural, but I think it's better to just name the abstraction. (If you take this suggestion, check elsewhere and be consistent.) AND/OR... You might also somehow incorporate the fact that this is a VM *function* that is represented: "Gunyah ioeventfd VM function(s)" > +MODULE_LICENSE("GPL"); > diff --git a/include/uapi/linux/gunyah.h b/include/uapi/linux/gunyah.h > index 5617dadc1c7b..f8482ff4cc55 100644 > --- a/include/uapi/linux/gunyah.h > +++ b/include/uapi/linux/gunyah.h > @@ -89,6 +89,23 @@ struct gh_vm_dtb_config { > */ > #define GH_FN_IRQFD 2 > > +/** > + * GH_FN_IOEVENTFD - register ioeventfd to trigger when VM faults on parameter What does "faults on parameter" mean? > + * > + * gh_fn_desc is filled with gh_fn_ioeventfd_arg > + * > + * Attaches an ioeventfd to a legal mmio address within the guest. A guest write > + * in the registered address will signal the provided event instead of triggering > + * an exit on the GH_VCPU_RUN ioctl. > + * > + * If GH_IOEVENTFD_DATAMATCH flag is set, the event will be signaled only if the > + * written value to the registered address is equal to datamatch in > + * struct gh_fn_ioeventfd_arg. > + * > + * Return: 0 > + */ > +#define GH_FN_IOEVENTFD 3 If you added another tab before 3, it will align more nicely with the next definition. (If you do that, add a tab in the other function definitions as well.) > + > #define GH_FN_MAX_ARG_SIZE 256 > > /** > @@ -118,6 +135,26 @@ struct gh_fn_irqfd_arg { > > #define GH_IOEVENTFD_DATAMATCH (1UL << 0) > > +/** > + * struct gh_fn_ioeventfd_arg - Arguments to create an ioeventfd function > + * @datamatch: data used when GH_IOEVENTFD_DATAMATCH is set > + * @addr: Address in guest memory > + * @len: Length of access > + * @fd: When ioeventfd is matched, this eventfd is written > + * @flags: If GH_IOEVENTFD_DATAMATCH flag is set, the event will be signaled > + * only if the written value to the registered address is equal to > + * @datamatch > + * @padding: padding bytes > + */ > +struct gh_fn_ioeventfd_arg { > + __u64 datamatch; > + __u64 addr; /* legal mmio address */ > + __u32 len; /* 1, 2, 4, or 8 bytes; or 0 to ignore length */ > + __s32 fd; > + __u32 flags; > + __u32 padding; > +}; > + > /** > * struct gh_fn_desc - Arguments to create a VM function > * @type: Type of the function. See GH_FN_* macro for supported types
WARNING: multiple messages have this Message-ID (diff)
From: Alex Elder <elder@linaro.org> To: Elliot Berman <quic_eberman@quicinc.com>, Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, Prakruthi Deepak Heragu <quic_pheragu@quicinc.com>, Jonathan Corbet <corbet@lwn.net> Cc: Murali Nalajala <quic_mnalajal@quicinc.com>, Trilok Soni <quic_tsoni@quicinc.com>, Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>, Carl van Schaik <quic_cvanscha@quicinc.com>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@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>, Will Deacon <will@kernel.org>, Andy Gross <agross@kernel.org>, Catalin Marinas <catalin.marinas@arm.com>, Jassi Brar <jassisinghbrar@gmail.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 v11 25/26] virt: gunyah: Add ioeventfd Date: Fri, 31 Mar 2023 09:27:46 -0500 [thread overview] Message-ID: <88a35ed3-78f9-c8ad-93b0-c7335e39a754@linaro.org> (raw) In-Reply-To: <20230304010632.2127470-26-quic_eberman@quicinc.com> On 3/3/23 7:06 PM, Elliot Berman wrote: > Allow userspace to attach an ioeventfd to an mmio address within the guest. > > Co-developed-by: Prakruthi Deepak Heragu <quic_pheragu@quicinc.com> > Signed-off-by: Prakruthi Deepak Heragu <quic_pheragu@quicinc.com> > Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> Mostly minor suggestions here. -Alex > --- > Documentation/virt/gunyah/vm-manager.rst | 2 +- > drivers/virt/gunyah/Kconfig | 9 ++ > drivers/virt/gunyah/Makefile | 1 + > drivers/virt/gunyah/gunyah_ioeventfd.c | 117 +++++++++++++++++++++++ > include/uapi/linux/gunyah.h | 37 +++++++ > 5 files changed, 165 insertions(+), 1 deletion(-) > create mode 100644 drivers/virt/gunyah/gunyah_ioeventfd.c > > diff --git a/Documentation/virt/gunyah/vm-manager.rst b/Documentation/virt/gunyah/vm-manager.rst > index a1dd70f0cbf6..cd41a705849f 100644 > --- a/Documentation/virt/gunyah/vm-manager.rst > +++ b/Documentation/virt/gunyah/vm-manager.rst > @@ -124,7 +124,7 @@ the VM starts. > The possible types are documented below: > > .. kernel-doc:: include/uapi/linux/gunyah.h > - :identifiers: GH_FN_VCPU gh_fn_vcpu_arg GH_FN_IRQFD gh_fn_irqfd_arg > + :identifiers: GH_FN_VCPU gh_fn_vcpu_arg GH_FN_IRQFD gh_fn_irqfd_arg GH_FN_IOEVENTFD gh_fn_ioeventfd_arg > > Gunyah VCPU API Descriptions > ---------------------------- > diff --git a/drivers/virt/gunyah/Kconfig b/drivers/virt/gunyah/Kconfig > index 2cde24d429d1..bd8e31184962 100644 > --- a/drivers/virt/gunyah/Kconfig > +++ b/drivers/virt/gunyah/Kconfig > @@ -35,3 +35,12 @@ config GUNYAH_IRQFD > on Gunyah virtual machine. > > Say Y/M here if unsure and you want to support Gunyah VMMs. > + > +config GUNYAH_IOEVENTFD > + tristate "Gunyah ioeventfd interface" > + depends on GUNYAH > + help > + Enable kernel support for creating ioeventfds which can alert userspace > + when a Gunyah virtual machine accesses a memory address. > + > + Say Y/M here if unsure and you want to support Gunyah VMMs. > diff --git a/drivers/virt/gunyah/Makefile b/drivers/virt/gunyah/Makefile > index 6cf756bfa3c2..7347b1470491 100644 > --- a/drivers/virt/gunyah/Makefile > +++ b/drivers/virt/gunyah/Makefile > @@ -8,3 +8,4 @@ obj-$(CONFIG_GUNYAH) += gunyah_rsc_mgr.o > > obj-$(CONFIG_GUNYAH_VCPU) += gunyah_vcpu.o > obj-$(CONFIG_GUNYAH_IRQFD) += gunyah_irqfd.o > +obj-$(CONFIG_GUNYAH_IOEVENTFD) += gunyah_ioeventfd.o > diff --git a/drivers/virt/gunyah/gunyah_ioeventfd.c b/drivers/virt/gunyah/gunyah_ioeventfd.c > new file mode 100644 > index 000000000000..517f55706ed9 > --- /dev/null > +++ b/drivers/virt/gunyah/gunyah_ioeventfd.c > @@ -0,0 +1,117 @@ > +// SPDX-License-Identifier: GPL-2.0-only > +/* > + * Copyright (c) 2022-2023 Qualcomm Innovation Center, Inc. All rights reserved. > + */ > + > +#include <linux/eventfd.h> > +#include <linux/file.h> > +#include <linux/fs.h> > +#include <linux/gunyah.h> > +#include <linux/gunyah_vm_mgr.h> > +#include <linux/module.h> > +#include <linux/printk.h> > + > +#include <uapi/linux/gunyah.h> > + > +struct gh_ioeventfd { > + struct gh_vm_function_instance *f; > + struct gh_vm_io_handler io_handler; > + > + struct eventfd_ctx *ctx; > +}; > + > +static int gh_write_ioeventfd(struct gh_vm_io_handler *io_dev, u64 addr, u32 len, u64 data) > +{ > + struct gh_ioeventfd *iofd = container_of(io_dev, struct gh_ioeventfd, io_handler); > + I think it's interesting that this signals an event even if len is zero. I'm not saying it's wrong, just interesting... > + eventfd_signal(iofd->ctx, 1); > + return 0; > +} > + > +static struct gh_vm_io_handler_ops io_ops = { > + .write = gh_write_ioeventfd, > +}; > + > +static long gh_ioeventfd_bind(struct gh_vm_function_instance *f) > +{ > + const struct gh_fn_ioeventfd_arg *args = f->argp; > + struct eventfd_ctx *ctx = NULL; No need to initialize ctx. > + struct gh_ioeventfd *iofd; > + int ret; > + > + if (f->arg_size != sizeof(*args)) > + return -EINVAL; > + > + /* must be natural-word sized, or 0 to ignore length */ > + switch (args->len) { > + case 0: > + case 1: > + case 2: > + case 4: > + case 8: > + break; > + default: > + return -EINVAL; > + } > + > + /* check for range overflow */ > + if (args->addr + args->len < args->addr) I think you could use: if (overflows_type(args->addr + args->len, args->addr)) This is a relatively recent addition (and I haven't been using it myself yet) but it's meant for this purpose. Consider using it and its relatives here and anywhere else you're making this kind of check. > + return -EINVAL; > + > + /* ioeventfd with no length can't be combined with DATAMATCH */ > + if (!args->len && (args->flags & GH_IOEVENTFD_DATAMATCH)) > + return -EINVAL; > + Maybe check for invalid flags before before ensuring valid flags are used properly? > + /* All other flag bits are reserved for future use */ > + if (args->flags & ~GH_IOEVENTFD_DATAMATCH) > + return -EINVAL; > + > + ctx = eventfd_ctx_fdget(args->fd); > + if (IS_ERR(ctx)) > + return PTR_ERR(ctx); > + > + iofd = kzalloc(sizeof(*iofd), GFP_KERNEL); > + if (!iofd) { > + ret = -ENOMEM; > + goto err_eventfd; > + } > + > + f->data = iofd; > + iofd->f = f; > + > + iofd->ctx = ctx; > + > + if (args->flags & GH_IOEVENTFD_DATAMATCH) { > + iofd->io_handler.datamatch = true; > + iofd->io_handler.len = args->len; > + iofd->io_handler.data = args->datamatch; I think you might want to rename one or the other of these fields (datamatch or data). I might be wrong; I'll explain elsewhere what I mean. > + } > + iofd->io_handler.addr = args->addr; > + iofd->io_handler.ops = &io_ops; > + > + ret = gh_vm_add_io_handler(f->ghvm, &iofd->io_handler); > + if (ret) > + goto err_io_dev_add; > + > + return 0; > + > +err_io_dev_add: > + kfree(iofd); > +err_eventfd: > + eventfd_ctx_put(ctx); > + return ret; > +} > + > +static void gh_ioevent_unbind(struct gh_vm_function_instance *f) > +{ > + struct gh_ioeventfd *iofd = f->data; > + > + eventfd_ctx_put(iofd->ctx); It's not a big deal but I prefer to "undo" everything in the reverse order that they are originally "done". I.e., put the eventfd context after removing the I/O handler. > + gh_vm_remove_io_handler(iofd->f->ghvm, &iofd->io_handler); > + kfree(iofd); > +} > + > +DECLARE_GH_VM_FUNCTION_INIT(ioeventfd, GH_FN_IOEVENTFD, > + gh_ioeventfd_bind, gh_ioevent_unbind); > +MODULE_DESCRIPTION("Gunyah ioeventfds"); s/ioeventfds/ioeventfd/ I understand why you might want it to be plural, but I think it's better to just name the abstraction. (If you take this suggestion, check elsewhere and be consistent.) AND/OR... You might also somehow incorporate the fact that this is a VM *function* that is represented: "Gunyah ioeventfd VM function(s)" > +MODULE_LICENSE("GPL"); > diff --git a/include/uapi/linux/gunyah.h b/include/uapi/linux/gunyah.h > index 5617dadc1c7b..f8482ff4cc55 100644 > --- a/include/uapi/linux/gunyah.h > +++ b/include/uapi/linux/gunyah.h > @@ -89,6 +89,23 @@ struct gh_vm_dtb_config { > */ > #define GH_FN_IRQFD 2 > > +/** > + * GH_FN_IOEVENTFD - register ioeventfd to trigger when VM faults on parameter What does "faults on parameter" mean? > + * > + * gh_fn_desc is filled with gh_fn_ioeventfd_arg > + * > + * Attaches an ioeventfd to a legal mmio address within the guest. A guest write > + * in the registered address will signal the provided event instead of triggering > + * an exit on the GH_VCPU_RUN ioctl. > + * > + * If GH_IOEVENTFD_DATAMATCH flag is set, the event will be signaled only if the > + * written value to the registered address is equal to datamatch in > + * struct gh_fn_ioeventfd_arg. > + * > + * Return: 0 > + */ > +#define GH_FN_IOEVENTFD 3 If you added another tab before 3, it will align more nicely with the next definition. (If you do that, add a tab in the other function definitions as well.) > + > #define GH_FN_MAX_ARG_SIZE 256 > > /** > @@ -118,6 +135,26 @@ struct gh_fn_irqfd_arg { > > #define GH_IOEVENTFD_DATAMATCH (1UL << 0) > > +/** > + * struct gh_fn_ioeventfd_arg - Arguments to create an ioeventfd function > + * @datamatch: data used when GH_IOEVENTFD_DATAMATCH is set > + * @addr: Address in guest memory > + * @len: Length of access > + * @fd: When ioeventfd is matched, this eventfd is written > + * @flags: If GH_IOEVENTFD_DATAMATCH flag is set, the event will be signaled > + * only if the written value to the registered address is equal to > + * @datamatch > + * @padding: padding bytes > + */ > +struct gh_fn_ioeventfd_arg { > + __u64 datamatch; > + __u64 addr; /* legal mmio address */ > + __u32 len; /* 1, 2, 4, or 8 bytes; or 0 to ignore length */ > + __s32 fd; > + __u32 flags; > + __u32 padding; > +}; > + > /** > * struct gh_fn_desc - Arguments to create a VM function > * @type: Type of the function. See GH_FN_* macro for supported types _______________________________________________ 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-03-31 14:29 UTC|newest] Thread overview: 168+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-04 1:06 [PATCH v11 00/26] Drivers for gunyah hypervisor Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 01/26] docs: gunyah: Introduce Gunyah Hypervisor Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 02/26] dt-bindings: Add binding for gunyah hypervisor Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 03/26] gunyah: Common types and error codes for Gunyah hypercalls Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-31 14:24 ` Alex Elder 2023-03-31 14:24 ` Alex Elder 2023-04-03 19:44 ` Elliot Berman 2023-04-03 19:44 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 04/26] virt: gunyah: Add hypercalls to identify Gunyah Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:22 ` Srinivas Kandagatla 2023-03-21 14:22 ` Srinivas Kandagatla 2023-03-31 14:24 ` Alex Elder 2023-03-31 14:24 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 05/26] virt: gunyah: Identify hypervisor version Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 15:48 ` Srinivas Kandagatla 2023-03-21 15:48 ` Srinivas Kandagatla 2023-03-31 14:24 ` Alex Elder 2023-03-31 14:24 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 06/26] virt: gunyah: msgq: Add hypercalls to send and receive messages Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 15:49 ` Srinivas Kandagatla 2023-03-21 15:49 ` Srinivas Kandagatla 2023-03-31 14:25 ` Alex Elder 2023-03-31 14:25 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 07/26] mailbox: Add Gunyah message queue mailbox Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:22 ` Srinivas Kandagatla 2023-03-21 14:22 ` Srinivas Kandagatla 2023-03-31 14:25 ` Alex Elder 2023-03-31 14:25 ` Alex Elder 2023-04-03 20:15 ` Elliot Berman 2023-04-03 20:15 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 08/26] gunyah: rsc_mgr: Add resource manager RPC core Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:25 ` Alex Elder 2023-03-31 14:25 ` Alex Elder 2023-04-03 20:34 ` Elliot Berman 2023-04-03 20:34 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 09/26] gunyah: rsc_mgr: Add VM lifecycle RPC Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:25 ` Alex Elder 2023-03-31 14:25 ` Alex Elder 2023-04-03 21:09 ` Elliot Berman 2023-04-03 21:09 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 10/26] gunyah: vm_mgr: Introduce basic VM Manager Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-31 14:25 ` Alex Elder 2023-03-31 14:25 ` Alex Elder 2023-04-11 20:48 ` Elliot Berman 2023-04-11 20:48 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 11/26] gunyah: rsc_mgr: Add RPC for sharing memory Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 12/26] gunyah: vm_mgr: Add/remove user memory regions Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-24 18:37 ` Will Deacon 2023-03-24 18:37 ` Will Deacon 2023-04-11 20:34 ` Elliot Berman 2023-04-11 20:34 ` Elliot Berman 2023-04-11 21:19 ` Will Deacon 2023-04-11 21:19 ` Will Deacon 2023-04-12 20:48 ` Elliot Berman 2023-04-12 20:48 ` Elliot Berman 2023-04-13 9:54 ` Will Deacon 2023-04-13 9:54 ` Will Deacon 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-04-11 21:04 ` Elliot Berman 2023-04-11 21:04 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 13/26] gunyah: vm_mgr: Add ioctls to support basic non-proxy VM boot Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:24 ` Srinivas Kandagatla 2023-03-21 14:24 ` Srinivas Kandagatla 2023-04-11 21:07 ` Elliot Berman 2023-04-11 21:07 ` Elliot Berman 2023-04-11 21:09 ` Alex Elder 2023-04-11 21:09 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-04-11 21:16 ` Elliot Berman 2023-04-11 21:16 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 14/26] samples: Add sample userspace Gunyah VM Manager Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 15/26] gunyah: rsc_mgr: Add platform ops on mem_lend/mem_reclaim Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-21 14:23 ` Srinivas Kandagatla 2023-03-22 19:17 ` Elliot Berman 2023-03-22 19:17 ` Elliot Berman 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 16/26] firmware: qcom_scm: Register Gunyah platform ops Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-21 14:24 ` Srinivas Kandagatla 2023-03-21 14:24 ` Srinivas Kandagatla 2023-03-21 18:40 ` Elliot Berman 2023-03-21 18:40 ` Elliot Berman 2023-03-21 20:19 ` Srinivas Kandagatla 2023-03-21 20:19 ` Srinivas Kandagatla 2023-03-04 1:06 ` [PATCH v11 17/26] docs: gunyah: Document Gunyah VM Manager Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 18/26] virt: gunyah: Translate gh_rm_hyp_resource into gunyah_resource Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-04-18 0:25 ` Elliot Berman 2023-04-18 0:25 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 19/26] gunyah: vm_mgr: Add framework to add VM Functions Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:26 ` Alex Elder 2023-03-31 14:26 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 20/26] virt: gunyah: Add resource tickets Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder 2023-03-31 14:27 ` Alex Elder 2023-04-17 22:57 ` Elliot Berman 2023-04-17 22:57 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 21/26] virt: gunyah: Add IO handlers Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder 2023-03-31 14:27 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 22/26] virt: gunyah: Add proxy-scheduled vCPUs Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder 2023-03-31 14:27 ` Alex Elder 2023-04-17 22:41 ` Elliot Berman 2023-04-17 22:41 ` Elliot Berman 2023-04-18 12:46 ` Alex Elder 2023-04-18 12:46 ` Alex Elder 2023-04-18 17:18 ` Elliot Berman 2023-04-18 17:18 ` Elliot Berman 2023-04-18 17:31 ` Alex Elder 2023-04-18 17:31 ` Alex Elder 2023-04-18 18:35 ` Elliot Berman 2023-04-18 18:35 ` Elliot Berman 2023-03-04 1:06 ` [PATCH v11 23/26] virt: gunyah: Add hypercalls for sending doorbell Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder 2023-03-31 14:27 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 24/26] virt: gunyah: Add irqfd interface Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder 2023-03-31 14:27 ` Alex Elder 2023-04-17 22:55 ` Elliot Berman 2023-04-17 22:55 ` Elliot Berman 2023-04-18 12:55 ` Alex Elder 2023-04-18 12:55 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 25/26] virt: gunyah: Add ioeventfd Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:27 ` Alex Elder [this message] 2023-03-31 14:27 ` Alex Elder 2023-03-04 1:06 ` [PATCH v11 26/26] MAINTAINERS: Add Gunyah hypervisor drivers section Elliot Berman 2023-03-04 1:06 ` Elliot Berman 2023-03-31 14:24 ` [PATCH v11 00/26] Drivers for gunyah hypervisor Alex Elder 2023-03-31 14:24 ` Alex Elder
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=88a35ed3-78f9-c8ad-93b0-c7335e39a754@linaro.org \ --to=elder@linaro.org \ --cc=agross@kernel.org \ --cc=andersson@kernel.org \ --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=gregkh@linuxfoundation.org \ --cc=jassisinghbrar@gmail.com \ --cc=konrad.dybcio@linaro.org \ --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=quic_cvanscha@quicinc.com \ --cc=quic_eberman@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=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.