From: Gleb Natapov <gleb@scylladb.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@scylladb.com>,
Alex Williamson <alex.williamson@redhat.com>,
avi@cloudius-systems.com, corbet@lwn.net,
bruce.richardson@intel.com, linux-kernel@vger.kernel.org,
alexander.duyck@gmail.com, gleb@cloudius-systems.com,
stephen@networkplumber.org, vladz@cloudius-systems.com,
iommu@lists.linux-foundation.org, hjk@hansjkoch.de,
gregkh@linuxfoundation.org
Subject: Re: [RFC PATCH 2/2] vfio: Include no-iommu mode
Date: Sun, 11 Oct 2015 12:23:03 +0300 [thread overview]
Message-ID: <20151011092303.GA19867@scylladb.com> (raw)
In-Reply-To: <20151011091954.GA27451@redhat.com>
On Sun, Oct 11, 2015 at 12:19:54PM +0300, Michael S. Tsirkin wrote:
> > But since you must pass the same value to open(), you already know that
> > you're using noiommu.
> >
> > >VFIO_IOMMU_MAP_DMA, VFIO_IOMMU_ENABLE and VFIO_IOMMU_DISABLE
> > >will probably also fail ...
> > >
> >
> > Don't you have to call MAP_DMA to pin the memory?
>
> Well check it out - the patch in question doesn't implement this ioctl.
> In fact it doesn't implement anything except CHECK_EXTENSION.
>
> And this makes sense to me: MAP_DMA
> maps a virtual address to io address, and that doesn't
> work for the dummy iommu.
>
> You can pin memory using many other ways, including
> mlock and hugetlbfs.
>
mlock() does not pin memory.
--
Gleb.
next prev parent reply other threads:[~2015-10-11 9:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 18:40 [RFC PATCH 0/2] VFIO no-iommu Alex Williamson
2015-10-09 18:40 ` Alex Williamson
[not found] ` <20151009182228.14752.99700.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
2015-10-09 18:41 ` [RFC PATCH 1/2] vfio: Move vfio.c vfio_core.c Alex Williamson
2015-10-09 18:41 ` Alex Williamson
[not found] ` <20151009184103.14752.5250.stgit-GCcqpEzw8uZBDLzU/O5InQ@public.gmane.org>
2015-10-09 19:21 ` Greg KH
2015-10-09 19:21 ` Greg KH
2015-10-09 18:41 ` [RFC PATCH 2/2] vfio: Include no-iommu mode Alex Williamson
2015-10-09 18:41 ` Alex Williamson
2015-10-11 8:12 ` Avi Kivity
[not found] ` <561A19DE.8040302-VrcmuVmyx1hWk0Htik3J/w@public.gmane.org>
2015-10-11 8:57 ` Michael S. Tsirkin
2015-10-11 8:57 ` Michael S. Tsirkin
2015-10-11 9:03 ` Avi Kivity
[not found] ` <561A25D5.6020906-VrcmuVmyx1hWk0Htik3J/w@public.gmane.org>
2015-10-11 9:19 ` Michael S. Tsirkin
2015-10-11 9:19 ` Michael S. Tsirkin
2015-10-11 9:23 ` Gleb Natapov [this message]
2015-10-11 21:16 ` Alex Williamson
2015-10-11 21:16 ` Alex Williamson
2015-10-12 15:56 ` Stephen Hemminger
2015-10-12 16:23 ` Alex Williamson
[not found] ` <1444666999.4059.362.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-12 16:31 ` Avi Kivity
2015-10-12 16:31 ` Avi Kivity
2015-10-12 16:27 ` Michael S. Tsirkin
2015-10-12 16:27 ` Michael S. Tsirkin
[not found] ` <20151012191150-mutt-send-email-mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-12 17:46 ` Alex Williamson
2015-10-12 17:46 ` Alex Williamson
[not found] ` <1444672015.4059.380.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-12 18:08 ` Alex Williamson
2015-10-12 18:08 ` Alex Williamson
2015-10-11 17:29 ` [RFC PATCH 0/2] VFIO no-iommu Varun Sethi
2015-10-11 17:29 ` Varun Sethi
[not found] ` <BN1PR0301MB0627AEEF3B5B7E5FB87ECB29EA320-RQSpjbwlmjSD1ymB6+i1+JwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-10-11 18:23 ` Alex Williamson
2015-10-11 18:23 ` Alex Williamson
2015-10-11 18:28 ` Michael S. Tsirkin
2015-10-11 18:28 ` Michael S. Tsirkin
[not found] ` <20151011182809.GA8154-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-11 18:29 ` Michael S. Tsirkin
2015-10-11 18:29 ` Michael S. Tsirkin
[not found] ` <20151011212852-mutt-send-email-mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-11 19:25 ` Alex Williamson
2015-10-11 19:25 ` Alex Williamson
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=20151011092303.GA19867@scylladb.com \
--to=gleb@scylladb.com \
--cc=alex.williamson@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=avi@cloudius-systems.com \
--cc=avi@scylladb.com \
--cc=bruce.richardson@intel.com \
--cc=corbet@lwn.net \
--cc=gleb@cloudius-systems.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stephen@networkplumber.org \
--cc=vladz@cloudius-systems.com \
/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.