From: Keir Fraser <keir@xensource.com>
To: Derek Murray <Derek.Murray@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, xense-devel@lists.xensource.com
Subject: Re: [RFC] [0/4] User-space grants for Console and XenStore
Date: Wed, 02 May 2007 15:48:24 +0100 [thread overview]
Message-ID: <C25E6348.E49F%keir@xensource.com> (raw)
In-Reply-To: <9FDA406C-003B-4FEE-83D9-0B01E357BF4F@cl.cam.ac.uk>
On 2/5/07 15:38, "Derek Murray" <Derek.Murray@cl.cam.ac.uk> wrote:
> At present, I don't store the grant-refs in xenstore, because they
> are constant (always 0 for xenstore, 1 for the console). I suppose I
> can see an argument where two different tool stacks are used with
> different conventions, but the same console and xenstore daemons are
> used. The tricky part is getting the grant references out of the
> domain builder without changing the interface to xc_linux_build().
> Would it be reasonable to assume that the current versions of xend
> and libxc are consistent, and therefore the fixed grant references
> could be written into xenstore (from constants in the Python code) at
> the same time as the console and xenstore mfns are?
I would accept that degree of binding between libxenctrl.so and the Python
binding Xc.so, yes. The existing xenstore arguments/fields might already be
unhelpfully called grant-ref, by the way. :-) Very stupid of me if so.
You'll just have to be a bit imaginative about naming of new args/fields in
that case.
> This should be quite simple: if the call to xc_gnttab_open() fails,
> it could set a flag which determines the method to be used. All that
> needs to be done in the mean time is to add stub functions to
> xc_solaris.c - I'll do that.
It's as simple as try grant-table method, fall back to direct-map method,
then fail outright, isn't it? Maybe that's what you meant.
-- Keir
next prev parent reply other threads:[~2007-05-02 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 11:15 [RFC] [0/4] User-space grants for Console and XenStore Derek Murray
2007-05-02 12:15 ` John Levon
2007-05-02 12:29 ` Derek Murray
2007-05-02 12:46 ` Keir Fraser
2007-05-02 14:38 ` Derek Murray
2007-05-02 14:48 ` Keir Fraser [this message]
2007-05-02 15:33 ` Derek Murray
2007-05-07 8:46 ` Isaku Yamahata
2007-05-08 14:40 ` Derek Murray
2007-05-08 15:31 ` Isaku Yamahata
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=C25E6348.E49F%keir@xensource.com \
--to=keir@xensource.com \
--cc=Derek.Murray@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xense-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.