> On Wed, Jun 20, 2012 at 2:10 AM, Guan Xuetao <g...@mprc.pku.edu.cn> wrote: >> On Mon, 2012-06-18 at 19:59 +0000, Blue Swirl wrote: >> [snip] >>> >>> hw_error() also aborts, it would be nice to avoid that. However, the >>> situation is somewhat different from the instruction case, since only >>> privileged guest code (kernel) can write to hardware. The kernel can >>> also for example power off the machine. >> >> It's the same problem as cpu_abort. Warning information is enough here. >> Is there a global and simple way to do it, g_warning()? > > The users will probably not be very interested about any debugging > messages. In cases like this, two common ways are to use trace points > or debugging printf macros. > I see. I will re-consider all cpu_abort and hw_error calls.
Thanks & Regards. Guan Xuetao
