linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Joerg Roedel <joro@8bytes.org>,
	"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux-foundation.org>,
	Andrew Cooks <acooks@gmail.com>, Don Dutile <ddutile@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>,
	George Spelvin <linux@horizon.com>
Subject: Re: [RFC PATCH v2 1/2] pci: Create PCIe requester ID interface
Date: Thu, 03 Apr 2014 20:51:54 -0600	[thread overview]
Message-ID: <1396579914.3215.36.camel@ul30vt.home> (raw)
In-Reply-To: <CAErSpo5p+6yt8ZyVuLnJTiKAWZWq9ixQQu78nD-bNFkw4ntWmw@mail.gmail.com>

On Thu, 2014-04-03 at 15:48 -0600, Bjorn Helgaas wrote:
> [+cc George]
> 
> On Fri, Aug 2, 2013 at 10:59 AM, Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > ...
> > Great!  I'm still trying to figure out how to handle the quirk around
> > Intel PCI-to-PCI bridge on the root complex as just another quirk.  I
> > respin another version once I have that worked out.  Thanks,
> 
> Is anything happening here?  These buggy IOMMU/DMA source problems,
> e.g., [1], have been lingering a long time, and I don't know if we're
> stuck because I haven't been giving them enough attention, or if we
> don't really have a good solution yet.
> 
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=42679

Sorry, no.  This has completely dropped off my radar.  I'll try to
resurrect it and figure out how to move forward.  Thanks,

Alex


  reply	other threads:[~2014-04-04  2:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 21:03 [RFC PATCH v2 0/2] pci/iommu: PCIe requester ID interface Alex Williamson
2013-07-11 21:03 ` [RFC PATCH v2 1/2] pci: Create " Alex Williamson
2013-07-23 22:35   ` Bjorn Helgaas
2013-07-23 23:21     ` Alex Williamson
2013-07-24 15:03       ` Andrew Cooks
2013-07-24 15:50         ` Alex Williamson
2013-07-24 16:47       ` Bjorn Helgaas
2013-07-24 18:12         ` Alex Williamson
2013-07-24 23:24           ` Bjorn Helgaas
2013-07-25 17:56             ` Alex Williamson
2013-07-26 21:54               ` Bjorn Helgaas
2013-07-29 16:06                 ` Alex Williamson
2013-07-29 21:02                   ` Bjorn Helgaas
2013-07-29 22:32                     ` Alex Williamson
2013-08-01 22:08                       ` Bjorn Helgaas
2013-08-02 16:59                         ` Alex Williamson
2014-04-03 21:48                           ` Bjorn Helgaas
2014-04-04  2:51                             ` Alex Williamson [this message]
2014-04-04 15:00                               ` Bjorn Helgaas
2013-07-29 21:03                   ` Don Dutile
2013-07-29 22:55                     ` Alex Williamson
2013-07-24 20:42     ` Don Dutile
2013-07-24 21:22       ` Alex Williamson
2013-07-25 18:38         ` Don Dutile
2013-07-25 17:19       ` Bjorn Helgaas
2013-07-25 18:25         ` Don Dutile
2013-07-26 19:48           ` Bjorn Helgaas
2013-07-26 20:04             ` Don Dutile
2013-07-11 21:03 ` [RFC PATCH v2 2/2] iommu/intel: Make use of " Alex Williamson

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=1396579914.3215.36.camel@ul30vt.home \
    --to=alex.williamson@redhat.com \
    --cc=acooks@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=ddutile@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@horizon.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 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).