Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp620660imj; Thu, 7 Feb 2019 09:16:21 -0800 (PST) X-Google-Smtp-Source: AHgI3IY3FpUjetL+kMP0YxB9M8U9O1oEhQnGFxsYFkBBdQM5Ykr/b+Cj5y/hPMPFOJWdc0CWjOdZ X-Received: by 2002:a65:514c:: with SMTP id g12mr15633919pgq.169.1549559781432; Thu, 07 Feb 2019 09:16:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549559781; cv=none; d=google.com; s=arc-20160816; b=GEwXlDZfkJjt2lGYA+qlMl80FIVCAnqOxmvrzJBjzRayL2+TxmK3jnd5tNdrNcvlfv lfHJWxvPADweuHJB5TjY0dJ56DadTgXULErguaFsimkOOpQLZtw5VjN7HAef8P/TlIiw xd/4QfEbmkOl2TMFSK5Y4hGYuq5kepW0iZO7cUWl5jfw1OkhhUfx2wDD+BaFFidWvDaH 3eeV3+ToVCOWYMgnOMfZA3InZrFlcuMAV/ZLYmCIIyD2nQxtNoe8Pd1ce0ztKjDvNnkl +AesD4bV6hAb27POuTeBGOgO8vfxm9qze8jqRnIjq3otqjPq8WOLYaNvpwLsJRgQg0Io n/yA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from; bh=ojvx6Ih0v9ZF6n3qBmBOFBhNU6qB1XfCz/HbuX6IHu0=; b=a6t3MudYw/k7sh0nYQrCYE7mKTVkNufSLba2A46u7V+XyY2UbTw5/rudbneV7WFjXQ mFWAT820ySBNlY1bQD9iLmIOaS0eedjqARdj/2B9gOeAfEOOUhKo18vst485ZSLJIp0K /KT4Fc/F6/72c0wttG5X2hFnruW2TB1TGVNzPlko09lj/qsrPp/KfHjLZ/2QI2jOJGJe HwIsZwA66FudylH43Xr2QzttD+nd71rFvfgbHECV8m25CfmVXm2b7s3CEwdwhyTJZdHW 9T8l2f84WjsvHQngP41m8vAGOrM1+WoZxas9iax5w4oYOQTgWG31SgzoW9z7K8b+i6WP SE5A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j1si8747090pff.42.2019.02.07.09.16.04; Thu, 07 Feb 2019 09:16:21 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726788AbfBGRPx (ORCPT + 99 others); Thu, 7 Feb 2019 12:15:53 -0500 Received: from mail-wr1-f67.google.com ([209.85.221.67]:35245 "EHLO mail-wr1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726171AbfBGRPw (ORCPT ); Thu, 7 Feb 2019 12:15:52 -0500 Received: by mail-wr1-f67.google.com with SMTP id z18so709840wrh.2 for ; Thu, 07 Feb 2019 09:15:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=ojvx6Ih0v9ZF6n3qBmBOFBhNU6qB1XfCz/HbuX6IHu0=; b=HitlDOO834yBMvl9tOqRl1Vv6xHbT+AyvdUol9Wr0wSUe1E9jFx9PF8slILggqS+V/ fFvcR7/jIIczMYmnKH8JFPeojQ2fMsiA4RVkvz5Pf3zXL3dh/7hBDcwmAxJe7VkKgsfc JP6baroO4ib4NeEJESQrhJcyFzYM6TKPTfq0Mdl2vkCRavPK07uJR9FEqJvIvw06dRzm DT9tj8iOxUg5s/wf6RBfVyz+YWY75O0ojq8iBiPmsRqmi4lu49IPW7f1bPSsK6aJnH8e A64+6zOJFhIpK0acexJmOymT2E4iqGwYhYQM1JuXjH3gC+N8bbNlLsKH9fKOsmfjKGqp eSdw== X-Gm-Message-State: AHQUAuagjf6GeIHkrIdFz/LjMz34jLL4/mF0KPEWtvABDC7Q5UDCshX3 lmCBY1k43dDiE2GZ/aQpx6lWJQ== X-Received: by 2002:adf:f411:: with SMTP id g17mr11069772wro.160.1549559749871; Thu, 07 Feb 2019 09:15:49 -0800 (PST) Received: from vitty.brq.redhat.com (nat-pool-brq-t.redhat.com. [213.175.37.10]) by smtp.gmail.com with ESMTPSA id r12sm11256352wrt.76.2019.02.07.09.15.48 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 07 Feb 2019 09:15:49 -0800 (PST) From: Vitaly Kuznetsov To: lantianyu1986@gmail.com Cc: Lan Tianyu , joro@8bytes.org, mchehab+samsung@kernel.org, davem@davemloft.net, gregkh@linuxfoundation.org, nicolas.ferre@microchip.com, arnd@arndb.de, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, michael.h.kelley@microsoft.com, kys@microsoft.com, alex.williamson@redhat.com, sashal@kernel.org, dan.carpenter@oracle.com Subject: Re: [PATCH V3 2/3] HYPERV/IOMMU: Add Hyper-V stub IOMMU driver In-Reply-To: <1549553629-8414-3-git-send-email-Tianyu.Lan@microsoft.com> References: <1549553629-8414-1-git-send-email-Tianyu.Lan@microsoft.com> <1549553629-8414-3-git-send-email-Tianyu.Lan@microsoft.com> Date: Thu, 07 Feb 2019 18:15:47 +0100 Message-ID: <87a7j7wmd8.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org lantianyu1986@gmail.com writes: > From: Lan Tianyu > > On the bare metal, enabling X2APIC mode requires interrupt remapping > function which helps to deliver irq to cpu with 32-bit APIC ID. > Hyper-V doesn't provide interrupt remapping function so far and Hyper-V > MSI protocol already supports to deliver interrupt to the CPU whose > virtual processor index is more than 255. IO-APIC interrupt still has > 8-bit APIC ID limitation. > > This patch is to add Hyper-V stub IOMMU driver in order to enable > X2APIC mode successfully in Hyper-V Linux guest. The driver returns X2APIC > interrupt remapping capability when X2APIC mode is available. Otherwise, > it creates a Hyper-V irq domain to limit IO-APIC interrupts' affinity > and make sure cpus assigned with IO-APIC interrupt have 8-bit APIC ID. > > Define 24 IO-APIC remapping entries because Hyper-V only expose one > single IO-APIC and one IO-APIC has 24 pins according IO-APIC spec( > https://pdos.csail.mit.edu/6.828/2016/readings/ia32/ioapic.pdf). > > Signed-off-by: Lan Tianyu > --- > Change since v2: > - Improve comment about why save IO-APIC entry in the irq chip data. > - Some code improvement. > - Improve statement in the IOMMU Kconfig. > > Change since v1: > - Remove unused pr_fmt > - Make ioapic_ir_domain as static variable > - Remove unused variables cfg and entry in the hyperv_irq_remapping_alloc() > - Fix comments > --- > drivers/iommu/Kconfig | 8 ++ > drivers/iommu/Makefile | 1 + > drivers/iommu/hyperv-iommu.c | 194 ++++++++++++++++++++++++++++++++++++++++++ > drivers/iommu/irq_remapping.c | 3 + > drivers/iommu/irq_remapping.h | 1 + > 5 files changed, 207 insertions(+) > create mode 100644 drivers/iommu/hyperv-iommu.c > > diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig > index 45d7021..6090935 100644 > --- a/drivers/iommu/Kconfig > +++ b/drivers/iommu/Kconfig > @@ -437,4 +437,12 @@ config QCOM_IOMMU > help > Support for IOMMU on certain Qualcomm SoCs. > > +config HYPERV_IOMMU > + bool "Hyper-V x2APIC IRQ Handling" > + depends on HYPERV > + select IOMMU_API > + help > + Stub IOMMU driver to handle IRQs as to allow Hyper-V Linux > + guests to run with x2APIC mode enabled. > + > endif # IOMMU_SUPPORT > diff --git a/drivers/iommu/Makefile b/drivers/iommu/Makefile > index a158a68..8c71a15 100644 > --- a/drivers/iommu/Makefile > +++ b/drivers/iommu/Makefile > @@ -32,3 +32,4 @@ obj-$(CONFIG_EXYNOS_IOMMU) += exynos-iommu.o > obj-$(CONFIG_FSL_PAMU) += fsl_pamu.o fsl_pamu_domain.o > obj-$(CONFIG_S390_IOMMU) += s390-iommu.o > obj-$(CONFIG_QCOM_IOMMU) += qcom_iommu.o > +obj-$(CONFIG_HYPERV_IOMMU) += hyperv-iommu.o > diff --git a/drivers/iommu/hyperv-iommu.c b/drivers/iommu/hyperv-iommu.c > new file mode 100644 > index 0000000..d8572c5 > --- /dev/null > +++ b/drivers/iommu/hyperv-iommu.c > @@ -0,0 +1,194 @@ > +// SPDX-License-Identifier: GPL-2.0 > + > +/* > + * Hyper-V stub IOMMU driver. > + * > + * Copyright (C) 2019, Microsoft, Inc. > + * > + * Author : Lan Tianyu > + */ > + > +#include > +#include > +#include > +#include > +#include > + > +#include > +#include > +#include > +#include > + > +#include "irq_remapping.h" > + > +#ifdef CONFIG_IRQ_REMAP > + > +/* > + * According 82093AA IO-APIC spec , IO APIC has a 24-entry Interrupt > + * Redirection Table. Hyper-V exposes one single IO-APIC and so define > + * 24 IO APIC remmapping entries. > + */ > +#define IOAPIC_REMAPPING_ENTRY 24 > + > +static cpumask_t ioapic_max_cpumask = { CPU_BITS_NONE }; > +static struct irq_domain *ioapic_ir_domain; > + > +static int hyperv_ir_set_affinity(struct irq_data *data, > + const struct cpumask *mask, bool force) > +{ > + struct irq_data *parent = data->parent_data; > + struct irq_cfg *cfg = irqd_cfg(data); > + struct IO_APIC_route_entry *entry; > + int ret; > + > + /* Return error If new irq affinity is out of ioapic_max_cpumask. */ > + if (!cpumask_subset(mask, &ioapic_max_cpumask)) > + return -EINVAL; > + > + ret = parent->chip->irq_set_affinity(parent, mask, force); > + if (ret < 0 || ret == IRQ_SET_MASK_OK_DONE) > + return ret; > + > + entry = data->chip_data; > + entry->dest = cfg->dest_apicid; > + entry->vector = cfg->vector; > + send_cleanup_vector(cfg); > + > + return 0; > +} > + > +static struct irq_chip hyperv_ir_chip = { > + .name = "HYPERV-IR", > + .irq_ack = apic_ack_irq, > + .irq_set_affinity = hyperv_ir_set_affinity, > +}; > + > +static int hyperv_irq_remapping_alloc(struct irq_domain *domain, > + unsigned int virq, unsigned int nr_irqs, > + void *arg) > +{ > + struct irq_alloc_info *info = arg; > + struct irq_data *irq_data; > + struct irq_desc *desc; > + int ret = 0; > + > + if (!info || info->type != X86_IRQ_ALLOC_TYPE_IOAPIC || nr_irqs > 1) > + return -EINVAL; > + > + ret = irq_domain_alloc_irqs_parent(domain, virq, nr_irqs, arg); > + if (ret < 0) > + return ret; > + > + irq_data = irq_domain_get_irq_data(domain, virq); > + if (!irq_data) { > + irq_domain_free_irqs_common(domain, virq, nr_irqs); > + return -EINVAL; > + } > + > + irq_data->chip = &hyperv_ir_chip; > + > + /* > + * If there is interrupt remapping function of IOMMU, setting irq > + * affinity only needs to change IRTE of IOMMU. But Hyper-V doesn't > + * support interrupt remapping function, setting irq affinity of IO-APIC > + * interrupts still needs to change IO-APIC registers. But ioapic_ > + * configure_entry() will ignore value of cfg->vector and cfg-> > + * dest_apicid when IO-APIC's parent irq domain is not the vector > + * domain.(See ioapic_configure_entry()) In order to setting vector > + * and dest_apicid to IO-APIC register, IO-APIC entry pointer is saved > + * in the chip_data and hyperv_irq_remapping_activate()/hyperv_ir_set_ > + * affinity() set vector and dest_apicid directly into IO-APIC entry. > + */ > + irq_data->chip_data = info->ioapic_entry; > + > + /* > + * Hypver-V IO APIC irq affinity should be in the scope of > + * ioapic_max_cpumask because no irq remapping support. > + */ > + desc = irq_data_to_desc(irq_data); > + cpumask_copy(desc->irq_common_data.affinity, &ioapic_max_cpumask); > + > + return 0; > +} > + > +static void hyperv_irq_remapping_free(struct irq_domain *domain, > + unsigned int virq, unsigned int nr_irqs) > +{ > + irq_domain_free_irqs_common(domain, virq, nr_irqs); > +} > + > +static int hyperv_irq_remapping_activate(struct irq_domain *domain, > + struct irq_data *irq_data, bool reserve) > +{ > + struct irq_cfg *cfg = irqd_cfg(irq_data); > + struct IO_APIC_route_entry *entry = irq_data->chip_data; > + > + entry->dest = cfg->dest_apicid; > + entry->vector = cfg->vector; > + > + return 0; > +} > + > +static struct irq_domain_ops hyperv_ir_domain_ops = { > + .alloc = hyperv_irq_remapping_alloc, > + .free = hyperv_irq_remapping_free, > + .activate = hyperv_irq_remapping_activate, > +}; > + > +static int __init hyperv_prepare_irq_remapping(void) > +{ > + struct fwnode_handle *fn; > + int i; > + > + if (!hypervisor_is_type(x86_hyper_type) || I think this should be if (hypervisor_is_type(X86_HYPER_MS_HYPERV)) > + !x2apic_supported()) > + return -ENODEV; > + > + fn = irq_domain_alloc_named_id_fwnode("HYPERV-IR", 0); > + if (!fn) > + return -ENOMEM; > + > + ioapic_ir_domain = > + irq_domain_create_hierarchy(arch_get_ir_parent_domain(), > + 0, IOAPIC_REMAPPING_ENTRY, fn, > + &hyperv_ir_domain_ops, NULL); > + > + irq_domain_free_fwnode(fn); > + > + /* > + * Hyper-V doesn't provide irq remapping function for > + * IO-APIC and so IO-APIC only accepts 8-bit APIC ID. > + * Cpu's APIC ID is read from ACPI MADT table and APIC IDs > + * in the MADT table on Hyper-v are sorted monotonic increasingly. > + * APIC ID reflects cpu topology. There maybe some APIC ID > + * gaps when cpu number in a socket is not power of two. Prepare > + * max cpu affinity for IOAPIC irqs. Scan cpu 0-255 and set cpu > + * into ioapic_max_cpumask if its APIC ID is less than 256. > + */ > + for (i = 0; i < 256; i++) > + if (cpu_physical_id(i) < 256) > + cpumask_set_cpu(i, &ioapic_max_cpumask); > + > + return 0; > +} > + > +static int __init hyperv_enable_irq_remapping(void) > +{ > + return IRQ_REMAP_X2APIC_MODE; > +} > + > +static struct irq_domain *hyperv_get_ir_irq_domain(struct irq_alloc_info *info) > +{ > + if (info->type == X86_IRQ_ALLOC_TYPE_IOAPIC) > + return ioapic_ir_domain; > + else > + return NULL; > +} > + > +struct irq_remap_ops hyperv_irq_remap_ops = { > + .prepare = hyperv_prepare_irq_remapping, > + .enable = hyperv_enable_irq_remapping, > + .get_ir_irq_domain = hyperv_get_ir_irq_domain, > +}; > + > +#endif > diff --git a/drivers/iommu/irq_remapping.c b/drivers/iommu/irq_remapping.c > index b94ebd4..81cf290 100644 > --- a/drivers/iommu/irq_remapping.c > +++ b/drivers/iommu/irq_remapping.c > @@ -103,6 +103,9 @@ int __init irq_remapping_prepare(void) > else if (IS_ENABLED(CONFIG_AMD_IOMMU) && > amd_iommu_irq_ops.prepare() == 0) > remap_ops = &amd_iommu_irq_ops; > + else if (IS_ENABLED(CONFIG_HYPERV_IOMMU) && > + hyperv_irq_remap_ops.prepare() == 0) > + remap_ops = &hyperv_irq_remap_ops; > else > return -ENOSYS; > > diff --git a/drivers/iommu/irq_remapping.h b/drivers/iommu/irq_remapping.h > index 0afef6e..f8609e9 100644 > --- a/drivers/iommu/irq_remapping.h > +++ b/drivers/iommu/irq_remapping.h > @@ -64,6 +64,7 @@ struct irq_remap_ops { > > extern struct irq_remap_ops intel_irq_remap_ops; > extern struct irq_remap_ops amd_iommu_irq_ops; > +extern struct irq_remap_ops hyperv_irq_remap_ops; > > #else /* CONFIG_IRQ_REMAP */ -- Vitaly