From: Joerg Roedel <jroedel@suse.de>
To: Huang Rui <ray.huang@amd.com>
Cc: Xiaojian Du <xiaojian.du@amd.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
iommu@lists.linux-foundation.org,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH] iommu/amd: Fix iommu remap panic while amd_iommu is set to disable
Date: Tue, 16 Mar 2021 14:16:34 +0100 [thread overview]
Message-ID: <YFCvsort3oZGfDBy@suse.de> (raw)
In-Reply-To: <20210311142807.705080-1-ray.huang@amd.com>
Hi Huang,
On Thu, Mar 11, 2021 at 10:28:07PM +0800, Huang Rui wrote:
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index f0adbc48fd17..a08e885403b7 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -3862,7 +3862,7 @@ static int irq_remapping_select(struct irq_domain *d, struct irq_fwspec *fwspec,
> else if (x86_fwspec_is_hpet(fwspec))
> devid = get_hpet_devid(fwspec->param[0]);
>
> - if (devid < 0)
> + if (devid < 0 || !amd_iommu_rlookup_table)
> return 0;
The problem is deeper than this fix suggests. I prepared other fixes for
this particular problem. Please find them here:
https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git/log/?h=iommu-fixes
Regards,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <jroedel@suse.de>
To: Huang Rui <ray.huang@amd.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Joerg Roedel <joro@8bytes.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Xiaojian Du <xiaojian.du@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/amd: Fix iommu remap panic while amd_iommu is set to disable
Date: Tue, 16 Mar 2021 14:16:34 +0100 [thread overview]
Message-ID: <YFCvsort3oZGfDBy@suse.de> (raw)
In-Reply-To: <20210311142807.705080-1-ray.huang@amd.com>
Hi Huang,
On Thu, Mar 11, 2021 at 10:28:07PM +0800, Huang Rui wrote:
> diff --git a/drivers/iommu/amd/iommu.c b/drivers/iommu/amd/iommu.c
> index f0adbc48fd17..a08e885403b7 100644
> --- a/drivers/iommu/amd/iommu.c
> +++ b/drivers/iommu/amd/iommu.c
> @@ -3862,7 +3862,7 @@ static int irq_remapping_select(struct irq_domain *d, struct irq_fwspec *fwspec,
> else if (x86_fwspec_is_hpet(fwspec))
> devid = get_hpet_devid(fwspec->param[0]);
>
> - if (devid < 0)
> + if (devid < 0 || !amd_iommu_rlookup_table)
> return 0;
The problem is deeper than this fix suggests. I prepared other fixes for
this particular problem. Please find them here:
https://git.kernel.org/pub/scm/linux/kernel/git/joro/linux.git/log/?h=iommu-fixes
Regards,
Joerg
next prev parent reply other threads:[~2021-03-16 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:28 [PATCH] iommu/amd: Fix iommu remap panic while amd_iommu is set to disable Huang Rui
2021-03-11 14:28 ` Huang Rui
2021-03-16 13:16 ` Joerg Roedel [this message]
2021-03-16 13:16 ` Joerg Roedel
2021-03-16 13:36 ` Huang Rui
2021-03-16 13:36 ` Huang Rui
2021-03-16 15:00 ` Joerg Roedel
2021-03-16 15:00 ` Joerg Roedel
2021-03-17 10:46 ` Huang Rui
2021-03-17 10:46 ` Huang Rui
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=YFCvsort3oZGfDBy@suse.de \
--to=jroedel@suse.de \
--cc=alexander.deucher@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=stable@vger.kernel.org \
--cc=xiaojian.du@amd.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 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.