[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9F6FE96B71CF29479FF1CDC8046E15032808E0@039-SN1MPN1-003.039d.mgd.msft.net>
Date: Thu, 1 Dec 2011 14:02:06 +0000
From: Yoder Stuart-B08248 <B08248@...escale.com>
To: Chris Wright <chrisw@...hat.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC: David Gibson <dwg@....ibm.com>,
Alex Williamson <alex.williamson@...hat.com>,
"joerg.roedel@....com" <joerg.roedel@....com>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"agraf@...e.de" <agraf@...e.de>,
Wood Scott-B07421 <B07421@...escale.com>
Subject: RE: [PATCH 1/4] iommu: Add iommu_device_group callback and
iommu_group sysfs entry
> > That way the domain information is available generically (can be match
> > with pci_domain_nr() for example), and sysfs can then be layed out as
> >
> > /sys/bus/pci/groups/<domain>/<id>
> >
> > Which is nicer than having enormous id's
>
> Seems fine to me (although I missed /sys/bus/pci/groups/ introduction), except that I think
> the freescale folks aren't interested in PCI which is one reason why the thing is just an
> opaque id.
We are interested in PCI, but non-PCI as well. All DMA devices,
have a globally unique "logical I/O device number" (LIODN) which
will map to a group # for us.
Stuart
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists