All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Error reporting capabilities for libxc
Date: Tue, 26 Sep 2006 14:20:35 +0100	[thread overview]
Message-ID: <20060926132035.GB8885@redhat.com> (raw)
In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B202A3B1@paddington.ad.cl.cam.ac.uk>

On Tue, Sep 26, 2006 at 01:58:11PM +0100, Ian Pratt wrote:
> > On 26/9/06 12:45, "Stephen C. Tweedie" <sct@redhat.com> 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  -=| 

  reply	other threads:[~2006-09-26 13:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 12:58 Error reporting capabilities for libxc Ian Pratt
2006-09-26 13:20 ` Daniel P. Berrange [this message]
2006-10-23 18:00 ` Daniel P. Berrange
2006-10-23 19:17   ` Anthony Liguori
2006-10-23 19:27     ` Daniel P. Berrange
2006-10-23 20:04       ` Anthony Liguori
2006-10-23 20:08         ` Daniel P. Berrange
2006-10-23 20:54       ` Ian Pratt
2006-10-23 20:57         ` Daniel P. Berrange
2006-10-23 21:10           ` Ian Pratt
2006-10-23 21:14             ` Anthony Liguori
2006-10-23 21:28               ` Daniel P. Berrange
2006-10-23 21:38                 ` Anthony Liguori
2006-10-23 21:47                   ` John Levon
2006-10-24  9:15                     ` Daniel Veillard
2006-10-23 21:48                   ` Daniel P. Berrange
2006-10-24  7:47               ` Gerd Hoffmann
2006-10-24  9:07                 ` Keir Fraser
2006-10-24 10:26                   ` Gerd Hoffmann
2006-10-23 21:21             ` Daniel P. Berrange
2006-10-23 22:15               ` Ian Pratt
2006-10-23 23:05                 ` Daniel P. Berrange
2006-10-23 20:40   ` John Levon
2006-10-23 21:04   ` John Levon
2006-10-23 21:09     ` Daniel P. Berrange
  -- strict thread matches above, loose matches on Subject: below --
2006-09-22 20:31 Daniel P. Berrange
2006-09-26 11:45 ` Stephen C. Tweedie
2006-09-26 12:28   ` Keir Fraser
2006-09-26 13:18     ` Daniel P. Berrange
2006-09-26 18:40 ` Hollis Blanchard
2006-09-26 18:49   ` Daniel P. Berrange
2006-09-26 21:37   ` Muli Ben-Yehuda

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=20060926132035.GB8885@redhat.com \
    --to=berrange@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.