From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: andmike@us.ibm.com, Ram Pai <linuxram@us.ibm.com>,
mdroth@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
ram.n.pai@gmail.com, cai@lca.pw, tglx@linutronix.de,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
hch@lst.de, bauerman@linux.ibm.com, david@gibson.dropbear.id.au
Subject: Re: [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs
Date: Wed, 6 Nov 2019 13:06:37 -0500 [thread overview]
Message-ID: <20191106130558-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <265679db-9cb3-1660-0cf6-97f740b1b48b@ozlabs.ru>
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.
Shouldn't be hard to support: set up the iommu to allow everything
and ack the feature. Right?
> >
> > Ram Pai (2):
> > powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor.
> > powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell.
> >
> > arch/powerpc/platforms/pseries/iommu.c | 30 ++++++++++++++++++------------
> > 1 file changed, 18 insertions(+), 12 deletions(-)
> >
>
> --
> Alexey
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Ram Pai <linuxram@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org, benh@kernel.crashing.org,
david@gibson.dropbear.id.au, mpe@ellerman.id.au,
paulus@ozlabs.org, mdroth@linux.vnet.ibm.com, hch@lst.de,
andmike@us.ibm.com, sukadev@linux.vnet.ibm.com,
ram.n.pai@gmail.com, cai@lca.pw, tglx@linutronix.de,
bauerman@linux.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs
Date: Wed, 6 Nov 2019 13:06:37 -0500 [thread overview]
Message-ID: <20191106130558-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <265679db-9cb3-1660-0cf6-97f740b1b48b@ozlabs.ru>
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.
Shouldn't be hard to support: set up the iommu to allow everything
and ack the feature. Right?
> >
> > Ram Pai (2):
> > powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor.
> > powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell.
> >
> > arch/powerpc/platforms/pseries/iommu.c | 30 ++++++++++++++++++------------
> > 1 file changed, 18 insertions(+), 12 deletions(-)
> >
>
> --
> Alexey
next prev parent reply other threads:[~2019-11-06 18:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 21:28 [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs Ram Pai
2019-11-04 21:28 ` Ram Pai
2019-11-04 21:28 ` [RFC v1 1/2] powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor Ram Pai
2019-11-04 21:28 ` Ram Pai
2019-11-04 21:28 ` [RFC v1 2/2] powerpc/pseries/iommu: Use dma_iommu_ops for Secure VMs aswell Ram Pai
2019-11-04 21:28 ` Ram Pai
2019-11-07 10:26 ` Michael Ellerman
2019-11-07 10:26 ` Michael Ellerman
2019-11-08 5:49 ` Ram Pai
2019-11-08 5:49 ` Ram Pai
2019-11-06 1:58 ` [RFC v1 1/2] powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor Alexey Kardashevskiy
2019-11-06 1:58 ` Alexey Kardashevskiy
2019-11-06 17:01 ` Ram Pai
2019-11-06 17:01 ` Ram Pai
2019-11-07 5:58 ` Alexey Kardashevskiy
2019-11-07 5:58 ` Alexey Kardashevskiy
2019-11-07 10:29 ` Michael Ellerman
2019-11-07 10:29 ` Michael Ellerman
2019-11-08 6:05 ` Ram Pai
2019-11-08 6:05 ` Ram Pai
2019-11-06 1:59 ` [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs Alexey Kardashevskiy
2019-11-06 1:59 ` Alexey Kardashevskiy
2019-11-06 16:46 ` Ram Pai
2019-11-06 16:46 ` Ram Pai
2019-11-06 18:06 ` Michael S. Tsirkin [this message]
2019-11-06 18:06 ` Michael S. Tsirkin
2019-11-06 18:52 ` Michael Roth
2019-11-06 18:52 ` Michael Roth
2019-11-06 22:22 ` Ram Pai
2019-11-06 22:22 ` Ram Pai
2019-11-07 6:01 ` Alexey Kardashevskiy
2019-11-07 6:01 ` Alexey Kardashevskiy
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=20191106130558-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aik@ozlabs.ru \
--cc=andmike@us.ibm.com \
--cc=bauerman@linux.ibm.com \
--cc=cai@lca.pw \
--cc=david@gibson.dropbear.id.au \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=ram.n.pai@gmail.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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.