From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: dan.magenheimer@oracle.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: tmem docs
Date: Tue, 28 May 2013 10:49:10 -0400 [thread overview]
Message-ID: <20130528144910.GQ724@phenom.dumpdata.com> (raw)
In-Reply-To: <6035A0D088A63A46850C3988ED045A4B5C1E6591@BITCOM1.int.sbss.com.au>
On Tue, May 28, 2013 at 12:26:15AM +0000, James Harper wrote:
> > On Mon, May 27, 2013 at 09:14:09AM +0000, James Harper wrote:
> > > Where is the best place to read about tmem hypercall abi? Should I start
> > > with the Linux implementation?
> > >
> >
> > I'm not really answering your question here.. but if you didn't see these links,
> > take a look, they might help:
> > http://lists.xen.org/archives/html/xen-devel/2013-05/msg01892.html
> >
>
> That all tells me about how great tmem is, and some of the interfaces exposed by Linux, but I can't find anything about the interfaces exposed by Xen that Windows would need to use. It seems that the interface is fairly thin though, and I have a few Windows related problems to solve first before I can even think about making use of tmem.
Let's CC Dan here. He has a stash of documents on that.
But looking at the include/public/tmem.h it is very slim on comments. The ones
that are of interest to you (I think) are:
TMEM_DESTROY_POOL, TMEM_NEW_POOL, TMEM_PUT_PAGE, and TMEM_GET_PAGE.
>
> Thanks
>
> James
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
next prev parent reply other threads:[~2013-05-28 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 9:14 tmem docs James Harper
2013-05-27 11:14 ` Pasi Kärkkäinen
2013-05-28 0:26 ` James Harper
2013-05-28 14:49 ` Konrad Rzeszutek Wilk [this message]
2013-05-28 16:20 ` Dan Magenheimer
2013-05-28 16:40 ` Konrad Rzeszutek Wilk
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=20130528144910.GQ724@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=james.harper@bendigoit.com.au \
--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.