From: Alex Williamson <alex.williamson@redhat.com> To: joerg.roedel@amd.com, dwmw2@infradead.org Cc: iommu@lists.linux-foundation.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, dsahern@gmail.com Subject: [PATCH 0/2] Fix ACS path checking Date: Sat, 04 Aug 2012 12:08:46 -0600 [thread overview] Message-ID: <20120804180155.6144.83332.stgit@bling.home> (raw) David Ahern reported an oops caused by passing a NULL start device to pci_acs_path_enabled(). This can happen when a bus is created for sr-iov devices without an associated bridge. To handle this, skip over to the parent bus and look for a bridge there. Continue until we find something or reach the root bus. This works on my system, but still needs to be tested by David. I'd like to get this in for 3.6-rc2. Joerg, I notice that ACS isn't getting enabled on my AMD system on 3.6-rc1. I'll investigate more, but mention it in case you get to it first. Thanks, Alex --- Alex Williamson (2): amd-iommu: Fix ACS path checking intel-iommu: Fix ACS path checking drivers/iommu/amd_iommu.c | 25 ++++++++++++++++++++++--- drivers/iommu/intel-iommu.c | 25 ++++++++++++++++++++++--- 2 files changed, 44 insertions(+), 6 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Alex Williamson <alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> To: joerg.roedel-5C7GfCeVMHo@public.gmane.org, dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org Cc: linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, dsahern-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Subject: [PATCH 0/2] Fix ACS path checking Date: Sat, 04 Aug 2012 12:08:46 -0600 [thread overview] Message-ID: <20120804180155.6144.83332.stgit@bling.home> (raw) David Ahern reported an oops caused by passing a NULL start device to pci_acs_path_enabled(). This can happen when a bus is created for sr-iov devices without an associated bridge. To handle this, skip over to the parent bus and look for a bridge there. Continue until we find something or reach the root bus. This works on my system, but still needs to be tested by David. I'd like to get this in for 3.6-rc2. Joerg, I notice that ACS isn't getting enabled on my AMD system on 3.6-rc1. I'll investigate more, but mention it in case you get to it first. Thanks, Alex --- Alex Williamson (2): amd-iommu: Fix ACS path checking intel-iommu: Fix ACS path checking drivers/iommu/amd_iommu.c | 25 ++++++++++++++++++++++--- drivers/iommu/intel-iommu.c | 25 ++++++++++++++++++++++--- 2 files changed, 44 insertions(+), 6 deletions(-)
next reply other threads:[~2012-08-04 18:09 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-04 18:08 Alex Williamson [this message] 2012-08-04 18:08 ` [PATCH 0/2] Fix ACS path checking Alex Williamson 2012-08-04 18:08 ` [PATCH 1/2] intel-iommu: " Alex Williamson 2012-08-04 18:08 ` Alex Williamson 2012-08-06 4:51 ` David Ahern 2012-08-04 18:09 ` [PATCH 2/2] amd-iommu: " Alex Williamson 2012-08-04 18:09 ` Alex Williamson 2012-08-06 10:50 ` [PATCH 0/2] " Joerg Roedel 2012-08-06 10:50 ` Joerg Roedel 2012-08-06 12:20 ` Joerg Roedel 2012-08-06 12:20 ` Joerg Roedel 2012-08-06 14:23 ` Alex Williamson 2012-08-06 17:41 ` Joerg Roedel 2012-08-06 17:41 ` 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=20120804180155.6144.83332.stgit@bling.home \ --to=alex.williamson@redhat.com \ --cc=dsahern@gmail.com \ --cc=dwmw2@infradead.org \ --cc=iommu@lists.linux-foundation.org \ --cc=joerg.roedel@amd.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@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: linkBe 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.