iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Alex Williamson
	<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org,
	linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org
Subject: Re: [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges
Date: Tue, 30 Jul 2013 13:52:59 +0200	[thread overview]
Message-ID: <20130730115259.GL28811@8bytes.org> (raw)
In-Reply-To: <1373303240.2602.28.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>

(sorry for the delay)

On Mon, Jul 08, 2013 at 11:07:20AM -0600, Alex Williamson wrote:
> Where do we stand on this series?  You had a concern that the heuristic
> used in patch 1/ could be dangerous.  The suggestion for detecting the
> issue was actually from Bjorn who replied with his rationale.  Do you
> want to go in the direction of a fixed whitelist or do you agree that
> even if the heuristic breaks it provides better behavior than what we
> have now?  Thanks,

So if this workaround should still live in the IOMMU code (after your
discussion with Bjorn) you can either convince me that the heuristic
will never fail or you resend a version that uses a list of known to be
broken bridges to match against.


	Joerg

      parent reply	other threads:[~2013-07-30 11:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 18:40 [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Alex Williamson
2013-05-28 18:40 ` [PATCH v2 2/2] intel-iommu: Convert to iommu_pci_find_upstream + iommu_pci_is_pcie_bridge Alex Williamson
     [not found] ` <20130528183527.3318.5365.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-05-28 18:40   ` [PATCH v2 1/2] iommu: Quirked PCIe bridge test and search function Alex Williamson
2013-05-28 19:38     ` Stephen Hemminger
2013-05-28 19:53       ` Alex Williamson
2013-05-28 19:56         ` Stephen Hemminger
2013-05-28 20:15           ` Alex Williamson
2013-05-28 20:28             ` Stephen Hemminger
     [not found]     ` <20130528184020.3318.7800.stgit-xdHQ/5r00wBBDLzU/O5InQ@public.gmane.org>
2013-06-20 13:59       ` Joerg Roedel
2013-06-20 15:44         ` Alex Williamson
     [not found]           ` <1371743091.32709.52.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2013-06-20 16:15             ` Joerg Roedel
2013-06-26  4:20               ` Bjorn Helgaas
     [not found]                 ` <CAErSpo5_P9tPdmpq2XO-X-d5NUWFG8Nbm_byKOkd5d4b8UMcMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-26 18:45                   ` Alex Williamson
2013-06-26 19:11                     ` Bjorn Helgaas
2013-05-28 22:09   ` [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Bjorn Helgaas
2013-05-28 22:53   ` [PATCH v2 3/2] pci: Remove unused pci_find_upstream_pcie_bridge() Alex Williamson
2013-07-08 17:07   ` [PATCH v2 0/2] iommu/intel: Quirk non-compliant PCIe-to-PCI bridges Alex Williamson
     [not found]     ` <1373303240.2602.28.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2013-07-08 19:34       ` Bjorn Helgaas
     [not found]         ` <20130708193436.GA31985-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-07-08 20:49           ` Alex Williamson
2013-07-08 21:51             ` Bjorn Helgaas
     [not found]               ` <20130708215131.GA1168-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2013-07-09 18:27                 ` Alex Williamson
2013-07-09 20:10                   ` Bjorn Helgaas
2013-07-30 11:52       ` Joerg Roedel [this message]

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=20130730115259.GL28811@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).