[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191106164630.GB5201@oc0525413822.ibm.com>
Date: Wed, 6 Nov 2019 08:46:30 -0800
From: Ram Pai <linuxram@...ibm.com>
To: Alexey Kardashevskiy <aik@...abs.ru>
Cc: linuxppc-dev@...ts.ozlabs.org, benh@...nel.crashing.org,
david@...son.dropbear.id.au, mpe@...erman.id.au, paulus@...abs.org,
mdroth@...ux.vnet.ibm.com, hch@....de, andmike@...ibm.com,
sukadev@...ux.vnet.ibm.com, mst@...hat.com, ram.n.pai@...il.com,
cai@....pw, tglx@...utronix.de, bauerman@...ux.ibm.com,
linux-kernel@...r.kernel.org
Subject: RE: [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs
On Wed, Nov 06, 2019 at 12:59:50PM +1100, Alexey Kardashevskiy wrote:
>
>
> On 05/11/2019 08:28, Ram Pai wrote:
> > This patch series enables IOMMU support for pseries Secure VMs.
> >
> >
> > Tested using QEMU command line option:
> >
> > "-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4,
> > iommu_platform=on,disable-modern=off,disable-legacy=on"
> > and
> >
> > "-device virtio-blk-pci,scsi=off,bus=pci.0,
> > addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,
> > iommu_platform=on,disable-modern=off,disable-legacy=on"
>
>
> Worth mentioning that SLOF won't boot with such devices as SLOF does not know about iommu_platform=on.
I did see SLOF complaining, but that did not stop it from booting the guest.
My boot device was a virtio device, with iommu platform flag
enabled.
So I am not sure, under what conditions SLOF will fail to boot. Any
idea?
RP
Powered by blists - more mailing lists