From: "Yu, Zhang" <yu.c.zhang@linux.intel.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
"Keir (Xen.org)" <keir@xen.org>, "Tim (Xen.org)" <tim@xen.org>,
"JBeulich@suse.com" <JBeulich@suse.com>,
Kevin Tian <kevin.tian@intel.com>,
"Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: One question about the hypercall to translate gfn to mfn.
Date: Tue, 09 Dec 2014 18:37:17 +0800 [thread overview]
Message-ID: <5486D0DD.1000902@linux.intel.com> (raw)
In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD02578573A@AMSPEX01CL01.citrite.net>
On 12/9/2014 6:19 PM, Paul Durrant wrote:
> I think use of an raw mfn value currently works only because dom0 is using a 1:1 IOMMU mapping scheme. Is my understanding correct, or do you really need raw mfn values?
Thanks for your quick response, Paul.
Well, not exactly for this case. :)
In XenGT, our need to translate gfn to mfn is for GPU's page table,
which contains the translation between graphic address and the memory
address. This page table is maintained by GPU drivers, and our service
domain need to have a method to translate the guest physical addresses
written by the vGPU into host physical ones.
We do not use IOMMU in XenGT and therefore this translation may not
necessarily be a 1:1 mapping.
B.R.
Yu
next prev parent reply other threads:[~2014-12-09 10:37 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 10:10 One question about the hypercall to translate gfn to mfn Yu, Zhang
2014-12-09 10:19 ` Paul Durrant
2014-12-09 10:37 ` Yu, Zhang [this message]
2014-12-09 10:50 ` Jan Beulich
2014-12-10 1:07 ` Tian, Kevin
2014-12-10 8:39 ` Jan Beulich
2014-12-10 8:47 ` Tian, Kevin
2014-12-10 9:16 ` Jan Beulich
2014-12-10 9:51 ` Tian, Kevin
2014-12-10 10:07 ` Jan Beulich
2014-12-10 11:04 ` Malcolm Crossley
2014-12-10 8:50 ` Tian, Kevin
2014-12-09 10:51 ` Malcolm Crossley
2014-12-10 1:22 ` Tian, Kevin
2014-12-09 10:38 ` Jan Beulich
2014-12-09 10:46 ` Tim Deegan
2014-12-09 11:05 ` Paul Durrant
2014-12-09 11:11 ` Ian Campbell
2014-12-09 11:17 ` Paul Durrant
2014-12-09 11:23 ` Jan Beulich
2014-12-09 11:28 ` Malcolm Crossley
2014-12-09 11:29 ` Ian Campbell
2014-12-09 11:43 ` Paul Durrant
2014-12-10 1:48 ` Tian, Kevin
2014-12-10 10:11 ` Ian Campbell
2014-12-11 1:50 ` Tian, Kevin
2014-12-10 1:14 ` Tian, Kevin
2014-12-10 10:36 ` Jan Beulich
2014-12-11 1:45 ` Tian, Kevin
2014-12-10 10:55 ` Tim Deegan
2014-12-11 1:41 ` Tian, Kevin
2014-12-11 16:46 ` Tim Deegan
2014-12-12 7:24 ` Tian, Kevin
2014-12-12 10:54 ` Jan Beulich
2014-12-15 6:25 ` Tian, Kevin
2014-12-15 8:44 ` Jan Beulich
2014-12-15 9:05 ` Tian, Kevin
2014-12-15 9:22 ` Jan Beulich
2014-12-15 11:16 ` Tian, Kevin
2014-12-15 11:27 ` Jan Beulich
2014-12-15 15:22 ` Stefano Stabellini
2014-12-15 16:01 ` Jan Beulich
2014-12-15 16:15 ` Stefano Stabellini
2014-12-15 16:28 ` David Vrabel
2014-12-15 16:28 ` Jan Beulich
2014-12-18 15:46 ` Tim Deegan
2015-01-06 8:56 ` Tian, Kevin
2015-01-08 12:43 ` Tim Deegan
2015-01-09 8:02 ` Tian, Kevin
2015-01-09 20:08 ` Konrad Rzeszutek Wilk
2015-01-12 11:14 ` David Vrabel
2014-12-11 21:29 ` Tim Deegan
2014-12-12 6:29 ` Tian, Kevin
2014-12-18 16:08 ` Tim Deegan
2014-12-18 17:01 ` Andrew Cooper
2015-01-05 15:49 ` George Dunlap
2015-01-06 8:42 ` Tian, Kevin
2015-01-06 10:35 ` Ian Campbell
2014-12-12 7:30 ` Tian, Kevin
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=5486D0DD.1000902@linux.intel.com \
--to=yu.c.zhang@linux.intel.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=tim@xen.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 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.