Am Mon, 21 Aug 2017 17:24:37 -0700 schrieb Gustavo Lima Chaves <[email protected]>:
> Hi, > > it seems recent kernel configs on distros (at least mine, on Fedora), > come with CONFIG_STRICT_DEVMEM=y, what seems the cause of the > following output: > > Feature Availability > ------------------------------ ------------------ > Number of CPUs > 1 ok > Long mode ok > x2APIC ok > > VT-x (VMX) ok > VMX without TXT ok > IA32_TRUE_*_CLTS ok > NMI exiting ok > Preemption timer ok > I/O bitmap ok > MSR bitmap ok > Secondary controls ok > Optional CR3 interception ok > Virtualize APIC access ok > RDTSCP ok > Unrestricted guest ok > EPT ok > 4-level page walk ok > EPTP write-back ok > 2M pages ok > 1G pages ok > INVEPT ok > Single or all-context ok > VM-exit save IA32_PAT ok > VM-exit load IA32_PAT ok > VM-exit save IA32_EFER ok > VM-exit load IA32_EFER ok > VM-entry load IA32_PAT ok > VM-entry load IA32_EFER ok > Activity state HLT ok > > VT-d (IOMMU #0) ok > Traceback (most recent call last): > File "./tools/jailhouse-hardware-check", line 236, in <module> > mmio = MMIO(iommu[n].base, iommu[n].size) > File "./tools/jailhouse-hardware-check", line 97, in __init__ > offset=base) > mmap.error: [Errno 1] Operation not permitted > > Any hints on how to surpass that without having to recompile kernels? This /dev/mem stuff is used for the IOMMUs which are also visible in sysfs. For Intel systems /sys/class/iommu/dmarN/intel-iommu/ On AMD it is in /sys/class/iommu/ivhdN/amd-iommu Not sure whether those files contain all the information currently used in the script. Patches welcome! Henning > Regards > > -- > Gustavo Lima Chaves > Intel - Open Source Technology Center > -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
