[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Error reporting capabilities for libxc



On Tue, Sep 26, 2006 at 01:58:11PM +0100, Ian Pratt wrote:
> > On 26/9/06 12:45, "Stephen C. Tweedie" <sct@xxxxxxxxxx> wrote:
> > 
> > >> So, I've prototyped a simple error reporting mechanism for 
> > libxc. The 
> > >> idea is we first define an enum for the broad classes of 
> > errors which can occur.
> > > ...
> > > 
> > >> Any way, the upshot of all this work:
> > >>   # xm create error
> > >>   Using config file "error".
> > >>   Error: [2, 'Kernel ELF architecture 3 does not match Xen 
> > >> architecture 62']
> > > 
> > > IMHO this is sorely needed.  Any comments from XenSource people?
> > 
> > I'd agree something like this is necessary in the 3.0.4 
> > timeframe. I'll let one of the guys more acquainted with xend 
> > comment in detail. There's also the question of how this will 
> > integrate with the proposed 'XenAPI'.
> 
> Yep, definitely needs to happen. However, I think we should at least
> discuss alternative potentially less clunky implementation methods.
> Perhaps we should use a thread local errno and error string variables?

Yes using thread locals instead of static vars is a good idea & should be
easy to implement behind the scenes. 

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.