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, Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v7 1/4] spapr_iommu: Make in-kernel TCE table optional
Date: Thu, 05 Jun 2014 15:06:30 +0200 [thread overview]
Message-ID: <53906B56.3080007@suse.de> (raw)
In-Reply-To: <5390119D.8040201@ozlabs.ru>
On 05.06.14 08:43, Alexey Kardashevskiy wrote:
> On 06/05/2014 03:49 PM, Alexey Kardashevskiy wrote:
>> POWER KVM supports an KVM_CAP_SPAPR_TCE capability which allows allocating
>> TCE tables in the host kernel memory and handle H_PUT_TCE requests
>> targeted to specific LIOBN (logical bus number) right in the host without
>> switching to QEMU. At the moment this is used for emulated devices only
>> and the handler only puts TCE to the table. If the in-kernel H_PUT_TCE
>> handler finds a LIOBN and corresponding table, it will put a TCE to
>> the table and complete hypercall execution. The user space will not be
>> notified.
>>
>> Upcoming VFIO support is going to use the same sPAPRTCETable device class
>> so KVM_CAP_SPAPR_TCE is going to be used as well. That means that TCE
>> tables for VFIO are going to be allocated in the host as well.
>> However VFIO operates with real IOMMU tables and simple copying of
>> a TCE to the real hardware TCE table will not work as guest physical
>> to host physical address translation is requited.
>>
>> So until the host kernel gets VFIO support for H_PUT_TCE, we better not
>> to register VFIO's TCE in the host.
>>
>> This adds a bool @kvm_accel flag to the sPAPRTCETable device telling
>> that sPAPRTCETable should not try allocating TCE table in the host kernel.
>> Instead, the table will be created in QEMU.
>>
>> This adds an kvm_accel parameter to spapr_tce_new_table() to let users
>> choose whether to use acceleration or not. At the moment it is enabled
>> for VIO and emulated PCI. Upcoming VFIO support will set it to false.
>>
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>>
>> This is a workaround but it lets me have one IOMMU device for VIO, emulated
>> PCI and VFIO which is a good thing.
>>
>> The other way around would be a new KVM_CAP_SPAPR_TCE_VFIO capability but
>> this needs kernel update.
>
> Never mind, I'll make it a capability. I'll post capability reservation
> patch separately.
Just rename the flag from "kvm_accel" to "vfio_accel", set it to true
for vfio and false for emulated devices. Then the spapr_iommu file can
check on the capability (and default to false for now, since it doesn't
exist yet).
That way you don't have to reserve a CAP today.
Alex
next prev parent reply other threads:[~2014-06-05 13:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 5:49 [Qemu-devel] [PATCH v7 0/4] vfio on spapr-ppc64 Alexey Kardashevskiy
2014-06-05 5:49 ` [Qemu-devel] [PATCH v7 1/4] spapr_iommu: Make in-kernel TCE table optional Alexey Kardashevskiy
2014-06-05 6:43 ` Alexey Kardashevskiy
2014-06-05 13:06 ` Alexander Graf [this message]
2014-06-05 13:10 ` Alexey Kardashevskiy
2014-06-05 13:15 ` Alexander Graf
2014-06-05 13:33 ` Alexey Kardashevskiy
2014-06-05 13:36 ` Alexander Graf
2014-06-05 14:33 ` Alexey Kardashevskiy
2014-06-05 16:51 ` Alexander Graf
2014-06-05 23:17 ` Alexey Kardashevskiy
2014-06-05 23:36 ` Alexander Graf
2014-06-05 23:48 ` Alexey Kardashevskiy
2014-06-06 3:38 ` Benjamin Herrenschmidt
2014-06-05 5:49 ` [Qemu-devel] [PATCH v7 2/4] vfio: Add vfio_container_spapr_get_info() Alexey Kardashevskiy
2014-06-05 19:27 ` Alex Williamson
2014-06-05 23:40 ` Alexey Kardashevskiy
2014-06-06 1:32 ` Gavin Shan
2014-06-05 5:50 ` [Qemu-devel] [PATCH v7 3/4] spapr_pci_vfio: Add spapr-pci-vfio-host-bridge to support vfio Alexey Kardashevskiy
2014-06-05 13:34 ` Alexander Graf
2014-06-05 14:37 ` Alexey Kardashevskiy
2014-06-05 5:50 ` [Qemu-devel] [PATCH v7 4/4] vfio: Enable for spapr Alexey Kardashevskiy
2014-06-05 19:31 ` Alex Williamson
2014-06-05 23:39 ` 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=53906B56.3080007@suse.de \
--to=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=gwshan@linux.vnet.ibm.com \
--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).