From: valmiki <valmikibow@gmail.com>
To: iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
linux-pci <linux-pci@vger.kernel.org>
Cc: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
kevin.tian@intel.com
Subject: VFIO on ARM64
Date: Tue, 12 Sep 2017 23:31:00 +0530 [thread overview]
Message-ID: <52a6fdbb-9a47-76c0-da59-89ac561b8ee3@gmail.com> (raw)
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
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
next reply other threads:[~2017-09-12 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 18:01 valmiki [this message]
2017-09-12 18:27 ` VFIO on ARM64 Alex Williamson
2017-09-12 18:27 ` Alex Williamson
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-03 13:56 ` valmiki
2017-12-04 11:12 ` Jean-Philippe Brucker
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=52a6fdbb-9a47-76c0-da59-89ac561b8ee3@gmail.com \
--to=valmikibow@gmail.com \
--cc=alex.williamson@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 \
/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 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.