On Thu, 11 Apr 2013, Sander Eikelenboom wrote:> > No. It depends a bit what you mean by "verbose debugging",
> > incidentally. QEMU has several commonly used logging options:
>
> Well since Xen has the option to be build with "make debug=y"
which also disables optimizations, enables extra asserts and makes it more
verbose.
> It could be handy to propagate that to the qemu-binary that is built in the
xen-tree to also be more verbose if it''s built as part of a debug
build.
>
> That way you can ask a user to build a debug build, and not have a user
edit to much source to enable all the defines.
>
> Apart from that the current xen-files in upstream qemu are much less
verbose than the old forked in tree qemu-traditional was, so that will also
require some adjustment.
>
> Would a "--enable-debug-xen" config option be acceptable ?
I think that''s not actually needed.
We should make better use of the following:
> > (2) the -d command line option, which lets the user enable
> > certain classes of logging by category (for example, this is
> > the best way to log "the guest did something weird which is
> > probably a guest bug" or "the guest tried to access
something
> > we don''t implement")
> > (3) tracepoints (see docs/tracing.txt)