[Qemu-devel] Re: QError conversion problems: putting errors in context

2010-02-17 Thread Luiz Capitulino
On Mon, 15 Feb 2010 19:42:29 +0100 Markus Armbruster arm...@redhat.com wrote: Anthony Liguori aligu...@linux.vnet.ibm.com writes: Thanks for the write-up. Here's my view of how error reporting ought to work: 0) A user tries to do something via some piece of code that serves as the

[Qemu-devel] Re: QError conversion problems: putting errors in context

2010-02-15 Thread Markus Armbruster
Anthony Liguori aligu...@linux.vnet.ibm.com writes: Hi Markus, On 02/12/2010 11:48 AM, Markus Armbruster wrote: Our QError conversions were pretty straightforward so far. For example, when we found monitor_printf(mon, device is not removable\n); in eject_device(), we

[Qemu-devel] Re: QError conversion problems: putting errors in context

2010-02-12 Thread Anthony Liguori
Hi Markus, On 02/12/2010 11:48 AM, Markus Armbruster wrote: Our QError conversions were pretty straightforward so far. For example, when we found monitor_printf(mon, device is not removable\n); in eject_device(), we created the obvious QError class for it: #define

[Qemu-devel] Re: QError conversion problems: putting errors in context

2010-02-12 Thread Luiz Capitulino
On Fri, 12 Feb 2010 15:39:07 -0600 Anthony Liguori aligu...@linux.vnet.ibm.com wrote: Hi Markus, On 02/12/2010 11:48 AM, Markus Armbruster wrote: Our QError conversions were pretty straightforward so far. For example, when we found monitor_printf(mon, device is not