From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Plan for error handling in QMP
Date: Fri, 27 Jul 2012 11:24:37 -0300 [thread overview]
Message-ID: <20120727112437.4fadfbef@doriath.home> (raw)
In-Reply-To: <87394e9m2q.fsf@codemonkey.ws>
On Thu, 26 Jul 2012 17:47:25 -0500
Anthony Liguori <anthony@codemonkey.ws> wrote:
> Luiz Capitulino <lcapitulino@redhat.com> writes:
>
> > On Thu, 26 Jul 2012 16:08:54 -0500
> > Anthony Liguori <anthony@codemonkey.ws> wrote:
> >
> >> Luiz Capitulino <lcapitulino@redhat.com> writes:
> >>
> >> > On Thu, 26 Jul 2012 15:43:58 -0300
> >> > Luiz Capitulino <lcapitulino@redhat.com> wrote:
> >> >
> >> >> On Thu, 26 Jul 2012 13:22:15 -0500
> >> >> anthony@codemonkey.ws wrote:
> >> >>
> >> >> >
> >> >> > Hi,
> >> >> >
> >> >> > We had a violent^Wheated discussion on IRC about how to move forward
> >> >> > with Luiz's proposed error series. I think we reached consensus. This
> >> >> > note attempts to outline that.
> >> >>
> >> >> This looks great to me, violent^W heated discussions can be so productive :)
> >> >>
> >> >> >
> >> >> > Principles
> >> >> > ----------
> >> >> > 1. Errors should be free formed strings with a class code
> >> >> >
> >> >> > 2. There should be a small number of class codes (10-15) added
> >> >> > strictly when there are specific users of a code.
> >> >
> >> > Btw, do we have a listing of those 10-15 errors already?
> >>
> >> See the clause: "added strictly when there are specific users".
> >>
> >> Users means consumers. So don't add an error type until someone cares
> >> to differientiate error reasons.
> >
> > What I meant is that, for 1.2 we want to reduce from 71 error codes to 10-15,
> > right? If that's right what are the 10-15 errors that won't be dropped?
> >
> > Or did I misunderstand?
>
> I meant drop it down to 5-6. The existing errors that libvirt cares
> about plus an UnknownError. #define all existing error codes to
> UnknownError and then at our leisure, we can introduce more generic
> classes and refactor errors incrementally.
That's great, I've already started working on this and should post the
series soon.
next prev parent reply other threads:[~2012-07-27 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:22 [Qemu-devel] Plan for error handling in QMP anthony
2012-07-26 18:43 ` Luiz Capitulino
2012-07-26 18:47 ` Luiz Capitulino
2012-07-26 21:08 ` Anthony Liguori
2012-07-26 21:14 ` Luiz Capitulino
2012-07-26 22:47 ` Anthony Liguori
2012-07-27 14:24 ` Luiz Capitulino [this message]
2012-07-26 20:41 ` Eric Blake
2012-07-27 7:08 ` Paolo Bonzini
2012-07-26 21:16 ` Richard W.M. Jones
2012-07-27 7:08 ` Markus Armbruster
2012-07-27 7:11 ` Paolo Bonzini
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=20120727112437.4fadfbef@doriath.home \
--to=lcapitulino@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).