From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Kamala Narasimhan <kamala.narasimhan@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xl: Check for dependencies in xl
Date: Fri, 14 Jan 2011 19:19:06 +0000 [thread overview]
Message-ID: <1295032746.12280.110.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimEu-and-4aaMUn+snhxS=cViKWweH6Jnbxpv10@mail.gmail.com>
On Fri, 2011-01-14 at 18:57 +0000, Kamala Narasimhan wrote:
>
> > The next thing after this xtl_createlogger_stdiostream(...) is a
> call to
> > libxl_ctx_init which will try and open the xenstore in the same way
> and
> > has error logging already so perhaps we should improve on that
> instead
> > of adding a separate check?
> >
> >
>
> Aren't we making the following assumptions in doing so -
>
> 1) xtl_createlogger_stdiostream would always be the first function
> called that uses xenstore.
You mean "libxl_ctx_init would always be..."?
In that case yes since that it is the function contains opens the
connection to xenstore so it must be called first. A libxl user
shouldn't need to see or use xenstore directly itself since libxl
encapsulates this.
xtl_createlogger_stdiostream does/can not use xenstore since it comes
from libxc which is beneath (or perhaps alongside) libxenstore in the
software stack.
> 2) There aren't likely to be other dependency checks to be added in
> future that might warrant a separate function to perform such checks?
It's not clear what other checks there will end up being but those which
are due to libxl's dependencies (e.g. xenstore) should be in a libxl
function. This could be a separate libxl_check_dependencies() but I
can't see any reason not to do it in libxl_ctx_init().
If xl has some dependency of its own independent of libxl which it is
useful to check then it would be appropriate to add those checks to xl
itself.
Ian.
next prev parent reply other threads:[~2011-01-14 19:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 16:57 [PATCH] xl: Check for dependencies in xl Kamala Narasimhan
2011-01-14 17:51 ` Ian Campbell
2011-01-14 18:57 ` Kamala Narasimhan
2011-01-14 19:19 ` Ian Campbell [this message]
2011-01-14 19:33 ` Kamala Narasimhan
2011-01-19 18:46 ` Kamala Narasimhan
2011-01-20 11:01 ` Stefano Stabellini
2011-01-20 14:10 ` Kamala Narasimhan
2011-01-20 14:15 ` Stefano Stabellini
2011-01-21 17:34 ` Ian Jackson
2011-01-21 17:37 ` Stefano Stabellini
2011-01-22 2:34 ` Kamala Narasimhan
2011-01-24 16:37 ` Gianni Tedesco
2011-01-24 17:26 ` Kamala Narasimhan
2011-01-24 17:32 ` Gianni Tedesco
2011-01-25 17:00 ` Ian Jackson
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=1295032746.12280.110.camel@localhost.localdomain \
--to=ian.campbell@eu.citrix.com \
--cc=kamala.narasimhan@gmail.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.