From: Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: jroedel-l3A5Bk7waGM@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Subject: Re: [PATCH 2/2] iommu/vt-d: Work around broken RMRR firmware entries
Date: Tue, 07 Oct 2014 08:59:24 +0800 [thread overview]
Message-ID: <54333AEC.6000603@linux.intel.com> (raw)
In-Reply-To: <1412244548-27617-3-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On 2014/10/2 18:09, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
>
> The VT-d specification states that an RMRR entry in the DMAR
> table needs to specify the full path to the device. This is
> also how newer Linux kernels implement it.
>
> Unfortunatly older drivers just match for the target device
> and not the full path to the device, so that BIOS vendors
> implement that behavior into their BIOSes to make them work
> with older Linux kernels. But those RMRR entries break on
> newer Linux kernels.
>
> Work around this issue by adding a fall-back into the RMRR
> matching code to match those old RMRR entries too.
>
> Signed-off-by: Joerg Roedel <jroedel-l3A5Bk7waGM@public.gmane.org>
> ---
> drivers/iommu/dmar.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iommu/dmar.c b/drivers/iommu/dmar.c
> index 6ba28b0..371ff33 100644
> --- a/drivers/iommu/dmar.c
> +++ b/drivers/iommu/dmar.c
> @@ -178,17 +178,33 @@ static bool dmar_match_pci_path(struct dmar_pci_notify_info *info, int bus,
> int i;
>
> if (info->bus != bus)
> - return false;
> + goto fallback;
> if (info->level != count)
> - return false;
> + goto fallback;
>
> for (i = 0; i < count; i++) {
> if (path[i].device != info->path[i].device ||
> path[i].function != info->path[i].function)
> - return false;
> + goto fallback;
> }
>
> return true;
> +
> +fallback:
> +
> + if (count != 1)
> + return false;
> +
> + i = info->level - 1;
> + if (bus == info->path[i].bus &&
> + path[0].device == info->path[i].device &&
> + path[0].function == info->path[i].function) {
> + pr_info(FW_BUG "RMRR entry for device %02x:%02x.%x is broken - applying workaround\n",
> + bus, path[0].device, path[0].function);
> + return true;
> + }
> +
> + return false;
> }
>
> /* Return: > 0 if match found, 0 if no match found, < 0 if error happens */
>
Hi Joerg,
Thanks for fixing this:)
Reviewed-by: Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Regards!
Gerry
WARNING: multiple messages have this Message-ID (diff)
From: Jiang Liu <jiang.liu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Cc: David Woodhouse <dwmw2@infradead.org>, jroedel@suse.de
Subject: Re: [PATCH 2/2] iommu/vt-d: Work around broken RMRR firmware entries
Date: Tue, 07 Oct 2014 08:59:24 +0800 [thread overview]
Message-ID: <54333AEC.6000603@linux.intel.com> (raw)
In-Reply-To: <1412244548-27617-3-git-send-email-joro@8bytes.org>
On 2014/10/2 18:09, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
>
> The VT-d specification states that an RMRR entry in the DMAR
> table needs to specify the full path to the device. This is
> also how newer Linux kernels implement it.
>
> Unfortunatly older drivers just match for the target device
> and not the full path to the device, so that BIOS vendors
> implement that behavior into their BIOSes to make them work
> with older Linux kernels. But those RMRR entries break on
> newer Linux kernels.
>
> Work around this issue by adding a fall-back into the RMRR
> matching code to match those old RMRR entries too.
>
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
> drivers/iommu/dmar.c | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iommu/dmar.c b/drivers/iommu/dmar.c
> index 6ba28b0..371ff33 100644
> --- a/drivers/iommu/dmar.c
> +++ b/drivers/iommu/dmar.c
> @@ -178,17 +178,33 @@ static bool dmar_match_pci_path(struct dmar_pci_notify_info *info, int bus,
> int i;
>
> if (info->bus != bus)
> - return false;
> + goto fallback;
> if (info->level != count)
> - return false;
> + goto fallback;
>
> for (i = 0; i < count; i++) {
> if (path[i].device != info->path[i].device ||
> path[i].function != info->path[i].function)
> - return false;
> + goto fallback;
> }
>
> return true;
> +
> +fallback:
> +
> + if (count != 1)
> + return false;
> +
> + i = info->level - 1;
> + if (bus == info->path[i].bus &&
> + path[0].device == info->path[i].device &&
> + path[0].function == info->path[i].function) {
> + pr_info(FW_BUG "RMRR entry for device %02x:%02x.%x is broken - applying workaround\n",
> + bus, path[0].device, path[0].function);
> + return true;
> + }
> +
> + return false;
> }
>
> /* Return: > 0 if match found, 0 if no match found, < 0 if error happens */
>
Hi Joerg,
Thanks for fixing this:)
Reviewed-by: Jiang Liu <jiang.liu@linux.intel.com>
Regards!
Gerry
next prev parent reply other threads:[~2014-10-07 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 10:09 [PATCH 0/2] iommu/vt-d: Make RMRR matching compatible with older kernels Joerg Roedel
2014-10-02 10:09 ` Joerg Roedel
[not found] ` <1412244548-27617-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-10-02 10:09 ` [PATCH 1/2] iommu/vt-d: Store bus information in RMRR PCI device path Joerg Roedel
2014-10-02 10:09 ` Joerg Roedel
2014-10-02 10:09 ` [PATCH 2/2] iommu/vt-d: Work around broken RMRR firmware entries Joerg Roedel
2014-10-02 10:09 ` Joerg Roedel
[not found] ` <1412244548-27617-3-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-10-07 0:59 ` Jiang Liu [this message]
2014-10-07 0:59 ` Jiang Liu
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=54333AEC.6000603@linux.intel.com \
--to=jiang.liu-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.