iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauerman@linux.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Mike Anderson <andmike@linux.ibm.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jason Wang <jasowang@redhat.com>,
	Alexey Kardashevskiy <aik@linux.ibm.com>,
	Ram Pai <linuxram@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Paul Mackerras <paulus@ozlabs.org>,
	iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
Date: Wed, 17 Apr 2019 18:42:44 -0300	[thread overview]
Message-ID: <878sw871gr.fsf@morokweng.localdomain> (raw)
Message-ID: <20190417214244.savWLyV1ghstzh7vF7OsWgZ0tWiFqqyjy6MGeIf_MHI@z> (raw)
In-Reply-To: <20190325005710.GC29295@umbus>


David Gibson <david@gibson.dropbear.id.au> writes:

> On Sat, Mar 23, 2019 at 05:01:35PM -0400, Michael S. Tsirkin wrote:
>> On Thu, Mar 21, 2019 at 09:05:04PM -0300, Thiago Jung Bauermann wrote:
>> > Michael S. Tsirkin <mst@redhat.com> writes:
> [snip]
>> > >> > Is there any justification to doing that beyond someone putting
>> > >> > out slow code in the past?
>> > >>
>> > >> The definition of the ACCESS_PLATFORM flag is generic and captures the
>> > >> notion of memory access restrictions for the device. Unfortunately, on
>> > >> powerpc pSeries guests it also implies that the IOMMU is turned on
>> > >
>> > > IIUC that's really because on pSeries IOMMU is *always* turned on.
>> > > Platform has no way to say what you want it to say
>> > > which is bypass the iommu for the specific device.
>> >
>> > Yes, that's correct. pSeries guests running on KVM are in a gray area
>> > where theoretically they use an IOMMU but in practice KVM ignores it.
>> > It's unfortunate but it's the reality on the ground today. :-/
>
> Um.. I'm not sure what you mean by this.  As far as I'm concerned
> there is always a guest-visible (paravirtualized) IOMMU, and that will
> be backed onto the host IOMMU when necessary.

There is, but vhost will ignore it and directly map the guest memory
when ACCESS_PLATFORM (the flag previously known as IOMMU_PLATFORM) isn't
set. From QEMU's hw/virtio/vhost.c:

static int vhost_dev_has_iommu(struct vhost_dev *dev)
{
    VirtIODevice *vdev = dev->vdev;

    return virtio_host_has_feature(vdev, VIRTIO_F_IOMMU_PLATFORM);
}

static void *vhost_memory_map(struct vhost_dev *dev, hwaddr addr,
                              hwaddr *plen, int is_write)
{
    if (!vhost_dev_has_iommu(dev)) {
        return cpu_physical_memory_map(addr, plen, is_write);
    } else {
        return (void *)(uintptr_t)addr;
    }
}

--
Thiago Jung Bauermann
IBM Linux Technology Center

_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-04-17 21:43 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-29 17:08 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted Thiago Jung Bauermann
2019-01-29 17:42 ` Thiago Jung Bauermann
2019-01-29 19:02   ` Michael S. Tsirkin
2019-01-30  2:24     ` Jason Wang
2019-01-30  2:36       ` Michael S. Tsirkin
2019-01-30  3:05         ` Jason Wang
2019-01-30  3:26           ` Michael S. Tsirkin
2019-01-30  7:44         ` Christoph Hellwig
2019-02-04 18:15           ` Thiago Jung Bauermann
2019-02-04 21:38             ` Michael S. Tsirkin
2019-02-05  7:24               ` Christoph Hellwig
     [not found]                 ` <20190205072407.GA4311-jcswGhMUV9g@public.gmane.org>
2019-02-05 16:13                   ` Michael S. Tsirkin
2019-03-26 16:53           ` Michael S. Tsirkin
2019-02-04 18:14     ` Thiago Jung Bauermann
2019-02-04 20:23       ` Michael S. Tsirkin
2019-03-20 16:13         ` Thiago Jung Bauermann
2019-03-20 21:17           ` Michael S. Tsirkin
2019-03-22  0:05             ` Thiago Jung Bauermann
2019-03-23 21:01               ` Michael S. Tsirkin
2019-03-25  0:57                 ` David Gibson
2019-04-17 21:42                   ` Thiago Jung Bauermann [this message]
2019-04-17 21:42                     ` Thiago Jung Bauermann
     [not found]                 ` <20190323165456-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2019-04-17 21:42                   ` Thiago Jung Bauermann
2019-04-17 21:42                     ` Thiago Jung Bauermann
2019-04-19 23:09                     ` Michael S. Tsirkin
2019-04-19 23:09                       ` Michael S. Tsirkin
2019-04-25  1:01                       ` Thiago Jung Bauermann
2019-04-25  1:01                         ` Thiago Jung Bauermann
     [not found]                         ` <875zr228zf.fsf-wxVGo8vDogbJvNEK5ZsId7p2dZbC/Bob@public.gmane.org>
2019-04-25  1:18                           ` Michael S. Tsirkin
2019-04-25  1:18                             ` Michael S. Tsirkin
2019-04-26 23:56                             ` Thiago Jung Bauermann
2019-04-26 23:56                               ` Thiago Jung Bauermann
2019-05-20 13:08                               ` Michael S. Tsirkin
2019-05-20 13:16                     ` Michael S. Tsirkin
2019-06-04  1:13                       ` Thiago Jung Bauermann
2019-06-04  1:42                         ` Michael S. Tsirkin
2019-06-28  1:58                           ` Thiago Jung Bauermann
2019-07-01 14:17                             ` Michael S. Tsirkin
2019-07-14  5:51                               ` Thiago Jung Bauermann
2019-07-15 14:35                                 ` Michael S. Tsirkin
2019-07-15 20:29                                   ` Thiago Jung Bauermann
2019-07-15 20:36                                     ` Michael S. Tsirkin
2019-07-15 22:03                                       ` Thiago Jung Bauermann
2019-07-15 22:16                                         ` Michael S. Tsirkin
2019-07-15 23:05                                           ` Thiago Jung Bauermann
2019-07-15 23:24                                         ` Benjamin Herrenschmidt
2019-07-18  3:39                                 ` Thiago Jung Bauermann
2019-08-10 18:57 ` Michael S. Tsirkin
2019-08-10 22:07   ` Ram Pai
2019-08-11  5:56     ` Christoph Hellwig
2019-08-11  6:46       ` Ram Pai
2019-08-11  8:44         ` Michael S. Tsirkin
2019-08-12 12:13         ` Christoph Hellwig
2019-08-12 20:29           ` Ram Pai
2019-08-11  8:42       ` Michael S. Tsirkin
2019-08-11  8:55       ` Michael S. Tsirkin
2019-08-12 12:15         ` Christoph Hellwig
2019-09-06  5:07           ` Michael S. Tsirkin
2019-08-12  9:51       ` David Gibson
2019-08-13 13:26         ` Christoph Hellwig
2019-08-13 14:24           ` David Gibson
2019-08-13 15:45             ` Ram Pai
2019-08-26 17:48               ` Ram Pai
2019-08-11  8:12     ` Michael S. Tsirkin

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=878sw871gr.fsf@morokweng.localdomain \
    --to=bauerman@linux.ibm.com \
    --cc=aik@linux.ibm.com \
    --cc=andmike@linux.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jasowang@redhat.com \
    --cc=jean-philippe.brucker@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxram@us.ibm.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=paulus@ozlabs.org \
    --cc=virtualization@lists.linux-foundation.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 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).