From: Neo Jia <cjia@nvidia.com>
To: Jike Song <jike.song@intel.com>
Cc: shuai.ruan@intel.com, kevin.tian@intel.com,
alex.williamson@redhat.com, kvm@vger.kernel.org,
qemu-devel@nongnu.org, Kirti Wankhede <kwankhede@nvidia.com>,
kraxel@redhat.com, pbonzini@redhat.com, zhiyuan.lv@intel.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU
Date: Thu, 3 Mar 2016 23:00:26 -0800 [thread overview]
Message-ID: <20160304070025.GA32070@nvidia.com> (raw)
In-Reply-To: <56D6A68A.50004@intel.com>
On Wed, Mar 02, 2016 at 04:38:34PM +0800, Jike Song wrote:
> On 02/24/2016 12:24 AM, Kirti Wankhede wrote:
> > + vgpu_dma->size = map->size;
> > +
> > + vgpu_link_dma(vgpu_iommu, vgpu_dma);
>
> Hi Kirti & Neo,
>
> seems that no one actually setup mappings for IOMMU here?
>
Hi Jike,
Yes.
The actual mapping should be done by the host kernel driver after calling the
translation/pinning API vgpu_dma_do_translate.
Thanks,
Neo
> >
>
> --
> Thanks,
> Jike
>
next prev parent reply other threads:[~2016-03-04 7:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:24 [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver Kirti Wankhede
2016-02-23 16:24 ` [Qemu-devel] [RFC PATCH v2 2/3] VFIO driver for vGPU device Kirti Wankhede
2016-02-23 16:24 ` [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU Kirti Wankhede
2016-03-02 8:38 ` Jike Song
2016-03-04 7:00 ` Neo Jia [this message]
2016-03-07 6:07 ` Jike Song
2016-03-08 0:31 ` Neo Jia
2016-03-10 3:10 ` Jike Song
2016-03-11 4:19 ` Neo Jia
2016-03-11 4:46 ` Tian, Kevin
2016-03-11 6:10 ` Neo Jia
2016-03-11 8:06 ` Tian, Kevin
2016-03-11 16:13 ` Alex Williamson
2016-03-11 16:55 ` Neo Jia
2016-03-11 17:56 ` Alex Williamson
2016-03-11 18:18 ` Neo Jia
2016-02-29 5:39 ` [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver Tian, Kevin
2016-02-29 23:17 ` Neo Jia
2016-03-01 3:10 ` Jike Song
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=20160304070025.GA32070@nvidia.com \
--to=cjia@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=jike.song@intel.com \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shuai.ruan@intel.com \
--cc=zhiyuan.lv@intel.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 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).