[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1422459450.5293.62.camel@infradead.org>
Date: Wed, 28 Jan 2015 15:37:30 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Feng Wu <feng.wu@...el.com>
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
x86@...nel.org, gleb@...nel.org, pbonzini@...hat.com,
joro@...tes.org, alex.williamson@...hat.com,
jiang.liu@...ux.intel.com, eric.auger@...aro.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
kvm@...r.kernel.org
Subject: Re: [v3 08/26] iommu, x86: Add intel_irq_remapping_capability() for
Intel
On Fri, 2014-12-12 at 23:14 +0800, Feng Wu wrote:
> Add the Intel side implementation for capability in
> struct irq_remap_ops.
>
> Signed-off-by: Feng Wu <feng.wu@...el.com>
> Reviewed-by: Jiang Liu <jiang.liu@...ux.intel.com>
> +static bool intel_irq_remapping_capability(enum irq_remap_cap cap)
> +{
> + struct dmar_drhd_unit *drhd;
> + struct intel_iommu *iommu;
> +
> + switch (cap) {
> + case IRQ_POSTING_CAP:
> + /*
> + * If 1) posted-interrupts is disabled by user
> + * or 2) irq remapping is disabled, posted-interrupts
> + * is not supported.
> + */
> + if (disable_irq_post || !irq_remapping_enabled)
> + return 0;
> +
> + for_each_iommu(iommu, drhd)
> + if (!cap_pi_support(iommu->cap))
> + return 0;
> +
If a new IOMMU is hotplugged now which doesn't support posted
interrupts, what happens?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@...el.com Intel Corporation
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5745 bytes)
Powered by blists - more mailing lists