From: Alexander Graf <agraf@suse.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v6 5/7] vfio: Introduce VFIO address spaces
Date: Fri, 23 May 2014 23:15:54 +0200 [thread overview]
Message-ID: <537FBA8A.6020704@suse.de> (raw)
In-Reply-To: <537F7473.6000200@ozlabs.ru>
On 23.05.14 18:16, Alexey Kardashevskiy wrote:
> On 05/23/2014 10:05 PM, Alexander Graf wrote:
>> On 23.05.14 14:03, Alexey Kardashevskiy wrote:
>>> On 05/23/2014 09:28 PM, Alexander Graf wrote:
>>>> On 23.05.14 06:59, Alexey Kardashevskiy wrote:
>>>>> From: David Gibson <david@gibson.dropbear.id.au>
>>>>>
>>>>> The only model so far supported for VFIO passthrough devices is the model
>>>>> usually used on x86, where all of the guest's RAM is mapped into the
>>>>> (host) IOMMU and there is no IOMMU visible in the guest.
>>>>>
>>>>> This patch begins to relax this model, introducing the notion of a
>>>>> VFIOAddressSpace. This represents a logical DMA address space which will
>>>>> be visible to one or more VFIO devices by appropriate mapping in the
>>>>> (host)
>>>>> IOMMU. Thus the currently global list of containers becomes local to
>>>>> a VFIOAddressSpace, and we verify that we don't attempt to add a VFIO
>>>>> group to multiple address spaces.
>>>>>
>>>>> For now, only one VFIOAddressSpace is created and used, corresponding to
>>>>> main system memory, that will change in future patches.
>>>>>
>>>>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>>>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>>> Don't we already have a DMA address space in the PCI bus? We could just use
>>>> that one instead, no?
>>> I do not know about x86, but for spapr that VFIOAddressSpace is nothing but
>>> wrapper around an AddressSpace from the SPAPR PHB.
>> So why do we need that wrapper? Can't we just use the PHB's AddressSpace?
>> There's a good chance I'm not grasping something here :).
>
> We cannot attach VFIO containers (aka "groups" or "PEs" for spapr) to
> AddressSpace, there is nothing like that in AddressSpace/MemoryRegion API
> as this container thing is local to VFIO.
Ok, please explain how this AddressSpace is different from the VFIO
device's parent's IOMMU DMA AddressSpace and why we need it.
Alex
next prev parent reply other threads:[~2014-05-23 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 4:59 [Qemu-devel] [PATCH v6 0/7] vfio: Prepare for SPAPR Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 1/7] memory: Sanity check that no listeners remain on a destroyed AddressSpace Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 2/7] int128: Add int128_exts64() Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 3/7] vfio: Fix 128 bit handling Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 4/7] vfio: Rework to have error paths Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 5/7] vfio: Introduce VFIO address spaces Alexey Kardashevskiy
2014-05-23 11:28 ` Alexander Graf
2014-05-23 12:03 ` Alexey Kardashevskiy
2014-05-23 12:05 ` Alexander Graf
2014-05-23 16:16 ` Alexey Kardashevskiy
2014-05-23 21:15 ` Alexander Graf [this message]
2014-05-24 3:12 ` Alexey Kardashevskiy
2014-05-25 10:16 ` Alexander Graf
2014-05-25 13:36 ` David Gibson
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 6/7] vfio: Create VFIOAddressSpace objects as needed Alexey Kardashevskiy
2014-05-23 4:59 ` [Qemu-devel] [PATCH v6 7/7] vfio: Add guest side IOMMU support 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=537FBA8A.6020704@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).