From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Kaushik Kumar Ram <kaushik@rice.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: question on iommu _map_page
Date: Thu, 27 May 2010 21:46:04 +0100 [thread overview]
Message-ID: <C824989C.210D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <285BD4A3-D6E2-422C-94B7-436822845BBC@rice.edu>
It looks like the person who implemented that never needed the read-only
case. We need a function to map pages into the iommu read-only and to call
that from the grant code.
A patch to just call iommu_map_page() for any kind of grant mapping would be
acceptable for now, if you want to submit a patch.
-- Keir
On 27/05/2010 21:37, "Kaushik Kumar Ram" <kaushik@rice.edu> wrote:
> Hi all,
>
> I am trying to use the VT-d support with a PV driver domain which performs
> network I/O on behalf of guest domains.
> When I initiate any network I/O it results in I/O page faults. On taking a
> closer look I find that iommu_map_page() is called only for writable pages
> from __gnttab_map_grant_ref(). This results in page faults during packet
> transmission since pages are mapped read-only in this case.
> When I remove this restriction, I can get it working without any page faults.
>
> Is this a bug? or am I missing something here? I am using the latest unstable
> version of Xen. This part of the source code hasn't changed in a long time.
>
> Thanks!
> -Kaushik
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-27 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 20:37 question on iommu _map_page Kaushik Kumar Ram
2010-05-27 20:46 ` Keir Fraser [this message]
2010-05-27 20:59 ` Kaushik Kumar Ram
2010-05-28 8:08 ` Keir Fraser
2010-05-28 23:20 ` Kaushik Kumar Ram
2010-05-29 7:29 ` Keir Fraser
2010-05-29 8:08 ` Kaushik Kumar Ram
2010-06-10 21:59 ` Kaushik Kumar Ram
2010-06-11 8:32 ` Keir Fraser
2010-07-02 6:22 ` Kaushik Kumar Ram
2010-07-02 7:13 ` Keir Fraser
2010-07-02 10:41 ` Keir Fraser
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=C824989C.210D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=kaushik@rice.edu \
--cc=xen-devel@lists.xensource.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).