qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: 阎淼 <yanmiaobest@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Dmitry Fleytman <dmitry@daynix.com>,
	jasowang@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] net/vmxnet3.c: fix a build error when enabling debug output
Date: Fri, 4 Dec 2015 18:24:02 +0800	[thread overview]
Message-ID: <CAPc5xaN4h2_5mrfggXek6-oMPRf0vfmeYw19t88WvGnOO-v8pQ@mail.gmail.com> (raw)
In-Reply-To: <87h9jzpjtf.fsf@blackfin.pond.sub.org>

2015-12-04 0:40 GMT+08:00 Markus Armbruster <armbru@redhat.com>:
> Eric Blake <eblake@redhat.com> writes:
>
>> On 12/02/2015 10:08 PM, Miao Yan wrote:
>>> Macro MAC_FMT and MAC_ARG are not defined, but used in vmxnet3_net_init().
>>> This will cause build error when debug level is raised in
>>> vmxnet3_debug.h (enable all VMXNET3_DEBUG_xxx).
>>>
>>> Use VMXNET_MF and VXMNET_MA instead.
>>>
>>> Signed-off-by: Miao Yan <yanmiaobest@gmail.com>
>>> ---
>>>  hw/net/vmxnet3.c | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/hw/net/vmxnet3.c b/hw/net/vmxnet3.c
>>> index 5e3a233..ea3d9b7 100644
>>> --- a/hw/net/vmxnet3.c
>>> +++ b/hw/net/vmxnet3.c
>>> @@ -2044,7 +2044,7 @@ static void vmxnet3_net_init(VMXNET3State *s)
>>>
>>>      s->link_status_and_speed = VMXNET3_LINK_SPEED | VMXNET3_LINK_STATUS_UP;
>>>
>>> -    VMW_CFPRN("Permanent MAC: " MAC_FMT, MAC_ARG(s->perm_mac.a));
>>> +    VMW_CFPRN("Permanent MAC: " VMXNET_MF, VMXNET_MA(s->perm_mac.a));
>>
>> This is a classic example of why dead code debug statements are evil.
>>
>> You should consider also providing a patch to hw/net/vmxnet_debug.h to
>> fix ALL of the broken debug macros in that file to instead use a sane
>> pattern, so that the format string is ALWAYS compiled and just optimized
>> out when debugging is disabled.
>>
>> Here's a conversion of one of the macros for an example of what to do:
>>
>> Instead of:
>>
>>> #ifdef VMXNET_DEBUG_CONFIG
>>> #define VMW_CFPRN(fmt, ...)                                                 \
>>>     do {                                                                    \
>>>         printf("[%s][CF][%s]: " fmt "\n", VMXNET_DEVICE_NAME, __func__,     \
>>>             ## __VA_ARGS__);                                                \
>>>     } while (0)
>>> #else
>>> #define VMW_CFPRN(fmt, ...) do {} while (0)
>>> #endif
>>
>> you should do:
>>
>> #ifdef VMXNET_DEBUG_CONFIG
>> # define VMXNET_DEBUG_CONFIG_FLAG 1
>> #else
>> # define VMXNET_DEBUG_CONFIG_FLAG 0
>> #endif
>> #define VMW_CFPRN(fmt, ...)                                       \
>>     do {                                                          \
>>         if (VMXNET_DEBUG_CONFIG_FLAG) {                           \
>>             printf("[%s][CF][%s]: " fmt "\n", VMXNET_DEVICE_NAME, \
>>                    __func__, ## __VA_ARGS__);                     \
>>         }                                                         \
>>     } while (0);
>>
>> With that pattern, VMW_CFPRN() will now always check that its arguments
>> can compile, even though it has no impact to the code size when
>> VMXNET_DEBUG_CONFIG is not defined.  Note that once you repair all of
>> the broken macros (I count 8 in that file), you may have some fallout of
>> other broken dead code that needs to be fixed.
>
> You may want to consider tracepoints instead of hand-rolled debugging
> macros: docs/tracing.txt.

Hi Markus,

  Thanks for your suggestion. It seems trace functions must have
fixed number of parameters, so, for example,
VMW_PRN("abc") and VMW_PRN("aaa %d", a) would need two trace functions,
right ?

  I looked at the code in vmxnet3.c, IMO not all debug output are
 suitable to be converted to trace points. Maybe I can work out a
 patch to fix the mmio part.

Miao

  reply	other threads:[~2015-12-04 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03  5:08 [Qemu-devel] [PATCH] net/vmxnet3.c: fix a build error when enabling debug output Miao Yan
2015-12-03  7:24 ` Dmitry Fleytman
2015-12-04  3:14   ` Jason Wang
2015-12-03 15:59 ` Eric Blake
2015-12-03 16:40   ` Markus Armbruster
2015-12-04 10:24     ` 阎淼 [this message]
2015-12-04 12:07       ` Markus Armbruster
     [not found]   ` <CAPc5xaOOb-FAxzXPgVrtOmqJvSs6Zwk7Rvy5qy3kFFMsnMF+2A@mail.gmail.com>
2015-12-04  7:05     ` 阎淼

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=CAPc5xaN4h2_5mrfggXek6-oMPRf0vfmeYw19t88WvGnOO-v8pQ@mail.gmail.com \
    --to=yanmiaobest@gmail.com \
    --cc=armbru@redhat.com \
    --cc=dmitry@daynix.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).