From: Keir Fraser <keir@xensource.com>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: RFC: Using grant table to give iomem permission
Date: Fri, 18 May 2007 15:45:27 +0100 [thread overview]
Message-ID: <C2737A97.F2B4%keir@xensource.com> (raw)
In-Reply-To: <1179497668.14376.31.camel@moonstone.uk.level5networks.com>
On 18/5/07 15:14, "Kieran Mansley" <kmansley@solarflare.com> wrote:
>>> Some questions from me:
>>> - does this approach seem sane?
>>
>> There's no reason you shouldn't be able to use GNTMAP_host_map as usual, and
>> do refcounting in the active grant entry, also as usual.
>
> OK. My reluctance to do that was simply that I wasn't sure if the
> operations that take place when doing a GNTMAP_host_map would conflict
> with those when doing an iomem_map. If you think they shouldn't, I'll
> give it a go.
I'm not sure what you mean.
> That raises one of my other questions which is how to test for it being
> a valid RAM page, as in the absence of it GNTMAP_iomem_map that's pretty
> much the only indicator that it's iomem we're dealing with. As I said,
> mfn_valid() doesn't seem to be sufficient.
Yes, I misled you here. You want the middle bit of get_page_from_l1e(). It
checks for !mfn_valid()||page_get_owner()==dom_io. Then you'd do an
iomem_access_permitted check passing in a pointer to the granting domain.
You should perhaps pull the core of get_page_from_l1e() into a supporting
function which you can then make available for common/grant_table.c to call
into.
-- Keir
next prev parent reply other threads:[~2007-05-18 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 14:01 RFC: Using grant table to give iomem permission Kieran Mansley
2007-05-18 14:05 ` Keir Fraser
2007-05-18 14:14 ` Kieran Mansley
2007-05-18 14:45 ` Keir Fraser [this message]
2007-05-18 14:50 ` Kieran Mansley
2007-05-18 16:03 ` Keir Fraser
[not found] <E1Hp33J-0006a6-QF@host-192-168-0-1-bcn-london>
2007-05-18 19:11 ` Lamia M. Youseff
2007-05-21 10:36 ` Kieran Mansley
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=C2737A97.F2B4%keir@xensource.com \
--to=keir@xensource.com \
--cc=kmansley@solarflare.com \
--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 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.