From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: David Scott <dave.scott@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: GNTTABOP_unmap_grant_ref doc
Date: Mon, 29 Jul 2013 10:00:21 +0100 [thread overview]
Message-ID: <CE1BEDB5.2EB36%keir.xen@gmail.com> (raw)
In-Reply-To: <1375087363.14896.12.camel@kazak.uk.xensource.com>
On 29/07/2013 09:42, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:
>>> If it turns out that I have misread the doc, I'll happily send a patch to
>>> improve the text (once I'm sure I understand what it should say...)
>>
>> From reading the implementation it woudl seem clear that host_addr is
>> actually needed.
>
> In fact I think you need to pass in whatever you passed to the original
> mapping operation, because op->flags here is not an argument from the
> unmap call but is actually a reference to the original flags used to
> make the mapping. So if you made the mapping with GNTMAP_host_map then
> you need to pass the host_addr on unmap. Likewise if you used
> GNTMAP_device_map then you need to specify dev_bus_addr.
>
> I've added Keir to the CC since he's the ultimate authority on these
> things.
The documentation is simply vague. GNTTABOP_unmap_grant_ref will only undo
mappings that it is given the address of. If you provide a zero address in
either field, that field is ignored. If you provide only zero addresses,
then GNTTABOP_unmap_grant_ref does no work at all!
But you now worked all this out already of course. ;)
-- Keir
next prev parent reply other threads:[~2013-07-29 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 12:49 GNTTABOP_unmap_grant_ref doc David Scott
2013-07-24 17:31 ` Stefano Stabellini
2013-07-29 8:42 ` Ian Campbell
2013-07-29 9:00 ` Keir Fraser [this message]
2013-07-24 18:30 ` David Vrabel
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=CE1BEDB5.2EB36%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=dave.scott@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.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.