From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device
Date: Wed, 20 Dec 2017 10:04:46 +0100 [thread overview]
Message-ID: <ada748a5-f174-89ab-9741-165b424c5485@redhat.com> (raw)
In-Reply-To: <344fb27b-1765-92e0-312f-6d5610925c5a@ozlabs.ru>
On 20/12/2017 02:47, Alexey Kardashevskiy wrote:
>> - if we foresee having more IOMMU devices in KVM, let's rename
>> KVM_DEV_VFIO_GROUP_SET_SPAPR_TCE to KVM_DEV_VFIO_GROUP_ATTACH_IOMMU and
>> add a new function
>>
>> int iommu_memory_region_get_kvm_fd(IOMMUMemoryRegion *iommu);
>>
>> that requires no object-type check in VFIO.
>
> This is how it started and the comment was that this KVM fd needs to have a
> well defined semantic which I struggle to provide.
I don't think the definition should be anything more than "it can be
passed to KVM_DEV_VFIO_GROUP_ATTACH_IOMMU". I'll discuss it with Alex
later today.
Paolo
next prev parent reply other threads:[~2017-12-20 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 5:18 [Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device Alexey Kardashevskiy
2017-12-12 5:46 ` Alex Williamson
2017-12-19 11:12 ` Paolo Bonzini
2017-12-19 14:09 ` Alex Williamson
2017-12-19 14:59 ` Paolo Bonzini
2017-12-20 1:47 ` Alexey Kardashevskiy
2017-12-20 9:04 ` Paolo Bonzini [this message]
2017-12-20 14:13 ` Alexey Kardashevskiy
2017-12-20 23:24 ` Paolo Bonzini
2018-01-19 6:03 ` David Gibson
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=ada748a5-f174-89ab-9741-165b424c5485@redhat.com \
--to=pbonzini@redhat.com \
--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).