From: "david@gibson.dropbear.id.au" <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"philmd@redhat.com" <philmd@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] ppc: remove excessive logging
Date: Mon, 16 Dec 2019 19:39:11 +1100 [thread overview]
Message-ID: <20191216083911.GE6242@umbus.fritz.box> (raw)
In-Reply-To: <ec67a070-77e2-08dc-9cc5-05907bbcbe79@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Mon, Dec 16, 2019 at 09:27:13AM +0100, Thomas Huth wrote:
> On 15/12/2019 22.15, Joakim Tjernlund wrote:
> [...]
> >> LOG_EXCP() is not enabled by default, you have to edit source to enable it
> >
> > LOG_EXCP is enabled on Gentoo, what about other distros?
>
> I don't think that this is enabled by any other distro. Why is this
> enabled on Gentoo at all? It really should not be enabled in builds that
> are supposed to be used by normal users. Have you tried to contact the
> package maintainers of the QEMU Gentoo package and asked them to disable
> it there again?
I concur. LOG_EXCP is definitely there for qemu developer debugging,
it's not intended for use in "normal" builds.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-16 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 12:13 [PATCH] ppc: remove excessive logging Joakim Tjernlund
2019-12-14 22:51 ` no-reply
2019-12-15 5:08 ` Philippe Mathieu-Daudé
2019-12-15 10:59 ` BALATON Zoltan
2019-12-15 21:15 ` Joakim Tjernlund
2019-12-16 8:27 ` Thomas Huth
2019-12-16 8:39 ` david [this message]
2019-12-16 8:52 ` Joakim Tjernlund
2019-12-17 0:31 ` David Gibson
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=20191216083911.GE6242@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=Joakim.Tjernlund@infinera.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).