From: Julien Grall <julien.grall@arm.com>
To: Shannon Zhao <shannon.zhao@linaro.org>,
linux-arm-kernel@lists.infradead.org, sstabellini@kernel.org
Cc: david.vrabel@citrix.com, devicetree@vger.kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
catalin.marinas@arm.com, will.deacon@arm.com,
peter.huangpeng@huawei.com, xen-devel@lists.xen.org,
zhaoshenglong@huawei.com
Subject: Re: [PATCH v10 06/17] Xen: ARM: Add support for mapping platform device mmio
Date: Wed, 6 Apr 2016 13:16:44 +0100 [thread overview]
Message-ID: <5704FE2C.5000902@arm.com> (raw)
In-Reply-To: <1459525755-36968-7-git-send-email-shannon.zhao@linaro.org>
Hi Shannon,
Sorry to come late in the review process.
On 01/04/2016 16:49, Shannon Zhao wrote:
> Add a bus_notifier for platform bus device in order to map the device
> mmio regions when DOM0 booting with ACPI.
>
> Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> ---
> drivers/xen/Makefile | 1 +
> drivers/xen/arm-device.c | 141 +++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 142 insertions(+)
> create mode 100644 drivers/xen/arm-device.c
>
> diff --git a/drivers/xen/Makefile b/drivers/xen/Makefile
> index 9b7a35c..415f286 100644
> --- a/drivers/xen/Makefile
> +++ b/drivers/xen/Makefile
> @@ -9,6 +9,7 @@ CFLAGS_features.o := $(nostackp)
>
> CFLAGS_efi.o += -fshort-wchar
>
> +dom0-$(CONFIG_ARM64) += arm-device.o
> dom0-$(CONFIG_PCI) += pci.o
> dom0-$(CONFIG_USB_SUPPORT) += dbgp.o
> dom0-$(CONFIG_XEN_ACPI) += acpi.o $(xen-pad-y)
> diff --git a/drivers/xen/arm-device.c b/drivers/xen/arm-device.c
> new file mode 100644
> index 0000000..76e26e5
> --- /dev/null
> +++ b/drivers/xen/arm-device.c
> @@ -0,0 +1,141 @@
> +/*
> + * Copyright (c) 2015, Linaro Limited, Shannon Zhao
> + *
> + * This program is free software; you can redistribute it and/or modify it
> + * under the terms and conditions of the GNU General Public License,
> + * version 2, as published by the Free Software Foundation.
> + *
> + * This program is distributed in the hope it will be useful, but WITHOUT
> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
> + * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
> + * more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program. If not, see <http://www.gnu.org/licenses/>.
> + */
> +
> +#include <linux/platform_device.h>
> +#include <linux/acpi.h>
> +#include <xen/xen.h>
> +#include <xen/page.h>
> +#include <xen/interface/memory.h>
> +#include <asm/xen/hypervisor.h>
> +#include <asm/xen/hypercall.h>
> +
> +static int xen_unmap_device_mmio(struct resource *resource, unsigned int count)
NITs:
There is multiple resource so s/resource/resources/.
Also the variable could be const.
> +{
> + unsigned int i, j, nr;
> + int rc = 0;
> + struct resource *r;
> + struct xen_remove_from_physmap xrp;
> +
> + for (i = 0; i < count; i++) {
> + r = &resource[i];
> + nr = DIV_ROUND_UP(resource_size(r), XEN_PAGE_SIZE);
> + if ((resource_type(r) != IORESOURCE_MEM) || (nr == 0))
> + continue;
> +
> + for (j = 0; j < nr; j++) {
> + xrp.domid = DOMID_SELF;
> + xrp.gpfn = XEN_PFN_DOWN(r->start) + j;
> + rc = HYPERVISOR_memory_op(XENMEM_remove_from_physmap,
> + &xrp);
> + if (rc)
> + return rc;
> + }
> + }
> +
> + return rc;
> +}
> +
> +static int xen_map_device_mmio(struct resource *resource, unsigned int count)
Ditto
> +{
> + unsigned int i, j, nr;
> + int rc = 0;
> + struct resource *r;
> + xen_pfn_t *gpfns;
> + xen_ulong_t *idxs;
> + int *errs;
> + struct xen_add_to_physmap_range xatp;
> +
> + for (i = 0; i < count; i++) {
> + r = &resource[i];
> + nr = DIV_ROUND_UP(resource_size(r), XEN_PAGE_SIZE);
> + if ((resource_type(r) != IORESOURCE_MEM) || (nr == 0))
> + continue;
> +
> + gpfns = kzalloc(sizeof(xen_pfn_t) * nr, GFP_KERNEL);
> + idxs = kzalloc(sizeof(xen_ulong_t) * nr, GFP_KERNEL);
> + errs = kzalloc(sizeof(int) * nr, GFP_KERNEL);
> + if (!gpfns || !idxs || !errs) {
> + kfree(gpfns);
> + kfree(idxs);
> + kfree(errs);
> + return -ENOMEM;
> + }
> +
> + for (j = 0; j < nr; j++) {
I would add a comment to explain that the regions are always mapped 1:1
to DOM0, and this is fine because the memory map for DOM0 is the same as
the host (except for the RAM).
> + gpfns[j] = XEN_PFN_DOWN(r->start) + j;
> + idxs[j] = XEN_PFN_DOWN(r->start) + j;
> + }
> +
> + xatp.domid = DOMID_SELF;
> + xatp.size = nr;
> + xatp.space = XENMAPSPACE_dev_mmio;
> +
> + set_xen_guest_handle(xatp.gpfns, gpfns);
> + set_xen_guest_handle(xatp.idxs, idxs);
> + set_xen_guest_handle(xatp.errs, errs);
> +
> + rc = HYPERVISOR_memory_op(XENMEM_add_to_physmap_range, &xatp);
> + kfree(gpfns);
> + kfree(idxs);
> + kfree(errs);
> + if (rc)
> + return rc;
Shouldn't we redo the mapping if the hypercall fails?
> + }
> +
> + return rc;
> +}
> +
> +static int xen_platform_notifier(struct notifier_block *nb,
> + unsigned long action, void *data)
> +{
> + struct platform_device *pdev = to_platform_device(data);
> + int r = 0;
> +
> + if (pdev->num_resources == 0 || pdev->resource == NULL)
> + return NOTIFY_OK;
> +
> + switch (action) {
> + case BUS_NOTIFY_ADD_DEVICE:
> + r = xen_map_device_mmio(pdev->resource, pdev->num_resources);
> + break;
> + case BUS_NOTIFY_DEL_DEVICE:
> + r = xen_unmap_device_mmio(pdev->resource, pdev->num_resources);
> + break;
> + default:
> + return NOTIFY_DONE;
> + }
> + if (r)
> + dev_err(&pdev->dev, "Platform: Failed to %s device %s MMIO!\n",
> + action == BUS_NOTIFY_ADD_DEVICE ? "map" :
> + (action == BUS_NOTIFY_DEL_DEVICE ? "unmap" : "?"),
> + pdev->name);
> +
> + return NOTIFY_OK;
> +}
> +
> +static struct notifier_block platform_device_nb = {
> + .notifier_call = xen_platform_notifier,
> +};
> +
> +static int __init register_xen_platform_notifier(void)
> +{
> + if (!xen_initial_domain() || acpi_disabled)
> + return 0;
> +
> + return bus_register_notifier(&platform_bus_type, &platform_device_nb);
> +}
> +
> +arch_initcall(register_xen_platform_notifier);
>
Regards,
--
Julien Grall
next prev parent reply other threads:[~2016-04-06 12:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 15:48 [PATCH v10 00/17] Add ACPI support for Xen Dom0 on ARM64 Shannon Zhao
2016-04-01 15:48 ` [PATCH v10 01/17] Xen: ACPI: Hide UART used by Xen Shannon Zhao
2016-04-01 19:21 ` Rafael J. Wysocki
2016-04-01 15:49 ` [PATCH v10 02/17] xen/grant-table: Move xlated_setup_gnttab_pages to common place Shannon Zhao
2016-04-06 11:40 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 03/17] Xen: xlate: Use page_to_xen_pfn instead of page_to_pfn Shannon Zhao
2016-04-06 11:42 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 04/17] arm/xen: Use xen_xlate_map_ballooned_pages to setup grant table Shannon Zhao
2016-04-06 11:43 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 05/17] xen: memory : Add new XENMAPSPACE type XENMAPSPACE_dev_mmio Shannon Zhao
2016-04-06 11:44 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 06/17] Xen: ARM: Add support for mapping platform device mmio Shannon Zhao
2016-04-06 12:16 ` Julien Grall [this message]
2016-04-07 1:37 ` Shannon Zhao
2016-04-07 10:32 ` Julien Grall
2016-04-07 11:25 ` Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 07/17] Xen: ARM: Add support for mapping AMBA " Shannon Zhao
2016-04-06 12:26 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 08/17] Xen: public/hvm: sync changes of HVM_PARAM_CALLBACK_VIA ABI from Xen Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 09/17] xen/hvm/params: Add a new delivery type for event-channel in HVM_PARAM_CALLBACK_IRQ Shannon Zhao
2016-04-06 12:29 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 10/17] arm/xen: Get event-channel irq through HVM_PARAM when booting with ACPI Shannon Zhao
2016-04-06 12:31 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 11/17] ARM: XEN: Move xen_early_init() before efi_init() Shannon Zhao
2016-04-06 12:35 ` Julien Grall
2016-04-01 15:49 ` [PATCH v10 12/17] ARM64: ACPI: Check if it runs on Xen to enable or disable ACPI Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 13/17] ARM: Xen: Document UEFI support on Xen ARM virtual platforms Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 14/17] XEN: EFI: Move x86 specific codes to architecture directory Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 15/17] ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 16/17] FDT: Add a helper to get the subnode by given name Shannon Zhao
2016-04-01 15:49 ` [PATCH v10 17/17] Xen: EFI: Parse DT parameters for Xen specific UEFI Shannon Zhao
2016-04-06 11:32 ` [PATCH v10 00/17] Add ACPI support for Xen Dom0 on ARM64 Julien Grall
2016-04-07 1:39 ` Shannon Zhao
2016-04-07 10:34 ` Julien Grall
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=5704FE2C.5000902@arm.com \
--to=julien.grall@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david.vrabel@citrix.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.huangpeng@huawei.com \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=will.deacon@arm.com \
--cc=xen-devel@lists.xen.org \
--cc=zhaoshenglong@huawei.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).