From: Joerg Roedel <joerg.roedel@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 3.2-stable] iommu/amd: Make sure IOMMU interrupts are re-enabled on resume
Date: Wed, 11 Apr 2012 18:29:39 +0200 [thread overview]
Message-ID: <20120411162938.GJ2428@amd.com> (raw)
In-Reply-To: <1334161546-11110-1-git-send-email-joerg.roedel@amd.com>
On Wed, Apr 11, 2012 at 06:25:46PM +0200, Joerg Roedel wrote:
> commit 9ddd592a191b32f2ee6c4b6ed2bd52665c3a49f5 upstream
>
> Unfortunatly the interrupts for the event log and the
> peripheral page-faults are only enabled at boot but not
> re-enabled at resume. Fix that for 3.2.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
Argh, please ignore this one, this patch does a little bit too much.
> ---
> drivers/iommu/amd_iommu_init.c | 27 ++++++++++++++++++++-------
> 1 files changed, 20 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c
> index 5c74179..c90a709 100644
> --- a/drivers/iommu/amd_iommu_init.c
> +++ b/drivers/iommu/amd_iommu_init.c
> @@ -1033,8 +1033,9 @@ static int iommu_setup_msi(struct amd_iommu *iommu)
> {
> int r;
>
> - if (pci_enable_msi(iommu->dev))
> - return 1;
> + r = pci_enable_msi(iommu->dev);
> + if (r)
> + return r;
>
> r = request_threaded_irq(iommu->dev->irq,
> amd_iommu_int_handler,
> @@ -1044,24 +1045,36 @@ static int iommu_setup_msi(struct amd_iommu *iommu)
>
> if (r) {
> pci_disable_msi(iommu->dev);
> - return 1;
> + return r;
> }
>
> iommu->int_enabled = true;
> - iommu_feature_enable(iommu, CONTROL_EVT_INT_EN);
>
> return 0;
> }
>
> static int iommu_init_msi(struct amd_iommu *iommu)
> {
> + int ret;
> +
> if (iommu->int_enabled)
> - return 0;
> + goto enable_faults;
>
> if (pci_find_capability(iommu->dev, PCI_CAP_ID_MSI))
> - return iommu_setup_msi(iommu);
> + ret = iommu_setup_msi(iommu);
> + else
> + ret = -ENODEV;
>
> - return 1;
> + if (ret)
> + return ret;
> +
> +enable_faults:
> + iommu_feature_enable(iommu, CONTROL_EVT_INT_EN);
> +
> + if (iommu->ppr_log != NULL)
> + iommu_feature_enable(iommu, CONTROL_PPFINT_EN);
> +
> + return 0;
> }
>
> /****************************************************************************
> --
> 1.7.5.4
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-04-11 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 16:25 [PATCH 3.2-stable] iommu/amd: Make sure IOMMU interrupts are re-enabled on resume Joerg Roedel
2012-04-11 16:29 ` Joerg Roedel [this message]
2012-04-11 16:40 ` Joerg Roedel
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=20120411162938.GJ2428@amd.com \
--to=joerg.roedel@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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: 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