On Sun, Oct 14, 2012 at 3:41 PM, Peter Maydell wrote:
> On 14 October 2012 15:02, Blue Swirl wrote:
>> On Sun, Oct 14, 2012 at 1:11 PM, Peter Maydell
>> wrote:
>>> One question that comes to mind -- should we include qemu-log.h
>>> in qemu-common.h (or some other common header?) rather than
>>>
On 14 October 2012 15:02, Blue Swirl wrote:
> On Sun, Oct 14, 2012 at 1:11 PM, Peter Maydell
> wrote:
>> One question that comes to mind -- should we include qemu-log.h
>> in qemu-common.h (or some other common header?) rather than
>> having to include qemu-log.h directly in lots of device model
On Sun, Oct 14, 2012 at 1:11 PM, Peter Maydell wrote:
> This patch series introduces a new logging category to
> qemu_log_mask(), for reporting situations which the device
> model can cope with but which indicate bugs in the guest.
> The most common cause of these is "guest tried to access
> a reg
This patch series introduces a new logging category to
qemu_log_mask(), for reporting situations which the device
model can cope with but which indicate bugs in the guest.
The most common cause of these is "guest tried to access
a register which doesn't exist". At the moment device models
use an in
