From: tgh <tianguanhua@ncic.ac.cn>
To: Kieran Mansley <kmansley@solarflare.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Getting a bus address for granted page in dom0
Date: Mon, 18 Jun 2007 17:44:55 +0800 [thread overview]
Message-ID: <46765417.1010104@ncic.ac.cn> (raw)
In-Reply-To: <1162913696.4141.28.camel@moonstone.uk.level5networks.com>
hi
I try to read the granttable code of xen,I am confused about some fields
in the struct grant_table,such as struct grant_entry **shared; struct
active_grant_entry **active; struct grant_mapping **maptrack; what are
the functions for the three structures ?
I am confused about it
could you help me
Thanks in advance
Kieran Mansley 写道:
> On Tue, 2006-11-07 at 11:26 +0000, Keir Fraser wrote:
>
>> Do you need to map the rings into dom0 addr space at all? If not just do a
>> GNTMAP_device_map yourself, and this will return a dev_bus_addr that you can
>> poke into hardware. If you go this route you avoid using the Linux DMA
>> interfaces altogether.
>>
>
> Thanks Keir, that was exactly what I was looking for.
>
> I've implemented this as an extra little helper function in
> xenbus_backend_client.c as an alternative to xenbus_map_ring() and
> xenbus_map_ring_valloc(). Is this something of wider use/interest? I'd
> be happy to submit a patch if so.
>
> Kieran
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
>
next prev parent reply other threads:[~2007-06-18 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 16:01 Getting a bus address for granted page in dom0 Kieran Mansley
2006-11-06 14:55 ` Kieran Mansley
2006-11-07 11:26 ` Keir Fraser
2006-11-07 15:34 ` Kieran Mansley
2007-06-18 9:44 ` tgh [this message]
2007-06-19 1:19 ` question about grant table tgh
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=46765417.1010104@ncic.ac.cn \
--to=tianguanhua@ncic.ac.cn \
--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.