From: Alex Williamson <alex.williamson@redhat.com>
To: valmiki <valmikibow@gmail.com>
Cc: iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-pci <linux-pci@vger.kernel.org>,
Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
kevin.tian@intel.com, Auger Eric <eric.auger@redhat.com>
Subject: Re: VFIO on ARM64
Date: Tue, 12 Sep 2017 12:27:56 -0600 [thread overview]
Message-ID: <20170912122756.2eb29bb2@t450s.home> (raw)
In-Reply-To: <52a6fdbb-9a47-76c0-da59-89ac561b8ee3@gmail.com>
[Cc +Eric Auger]
On Tue, 12 Sep 2017 23:31:00 +0530
valmiki <valmikibow@gmail.com> wrote:
> Hi, as per VFIO documentation i see that we need to see
> "/sys/bus/pci/devices/0000:06:0d.0/iommu_group" in order to find group
> in which PCI bus is attached.
> But as per drivers/pci/pci-sysfs.c in static struct attribute
> *pci_dev_attrs[], i don't see any such attribute.
> I tried enabling SMMUv2 driver and SMMU for PCIe node on our SOC, but
> this file doesn't show up and also in /sys/kernel/iommu_group i do not
> see "/sys/kernel/iommu_groups/17/devices/0000:00:1f.00" file, i see only
> PCIe root port device tree node in that group and not individual buses.
> So on ARM64 for showing these paths i.e show specific to each bus, does
> SMMU need any particular confguration (we have SMMUv2) ?
> Do we need any specific kernel configuration ?
>
>
> Regards,
> Valmiki
next prev parent reply other threads:[~2017-09-12 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 18:01 VFIO on ARM64 valmiki
2017-09-12 18:27 ` Alex Williamson [this message]
2017-09-13 1:20 ` Jean-Philippe Brucker
2017-09-13 17:38 ` valmiki
2017-09-13 18:57 ` Jean-Philippe Brucker
2017-12-03 13:56 ` Invalidation in SMMU v3 valmiki
2017-12-04 11:12 ` Jean-Philippe Brucker
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=20170912122756.2eb29bb2@t450s.home \
--to=alex.williamson@redhat.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=valmikibow@gmail.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).