From: Joe Perches <joe@perches.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
Matt Mooney <mfm@muteddisk.com>, Max Vozeler <max@hinterhof.net>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
usbip-devel@lists.sourceforge.net, devel@driverdev.osuosl.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] usbip: dump the port status difference
Date: Mon, 13 Jun 2011 15:12:26 -0700 [thread overview]
Message-ID: <1308003146.26699.43.camel@Joe-Laptop> (raw)
In-Reply-To: <4DF68159.1090206@freemail.hu>
On Mon, 2011-06-13 at 23:30 +0200, Németh Márton wrote:
> From: Márton Németh <nm127@freemail.hu>
>
> Change the dump function to
> really show the differences in the status bit changes
> +static void dump_port_status_diff(u32 prev_status, u32 new_status)
> {
> int i = 0;
> - pr_debug("status %08x:", status);
> + pr_debug("status %08x -> %08x:", prev_status, new_status);
> for (i = 0; i < 32; i++) {
> - if (status & (1 << i))
> - pr_debug(" %s", bit_desc[i]);
> + if (!(prev_status & (1 << i)) &&
> + new_status & (1 << i)) {
> + pr_debug(" +%s", bit_desc[i]);
> + } else if (prev_status & (1 << i) &&
> + !(new_status & (1 << i))) {
> + pr_debug(" -%s", bit_desc[i]);
> + } else if (prev_status & (1 << i) &&
> + new_status & (1 << i)) {
> + pr_debug(" %s", bit_desc[i]);
> + }
> }
> pr_debug("\n");
trivia:
I think the output isn't quite what you might expect.
It could be interleaved by pr_cont from a different
thread.
I think this might be a bit more readable as below and
this doesn't use implicit newlines by successive pr_<level>.
static void dump_port_status_diff(u32 old_status, u32 new_status)
{
int i = 0;
u32 bit = 1;
char change;
pr_debug("status old->new %08x -> %08x\n", old_status, new_status);
while (bit) {
u32 old = old_status & bit;
u32 new = new_status & bit;
char change;
if (!old && new)
change = '+';
else if (old && !new)
change = '-';
else
change = ' ';
if (old || new)
pr_debug(" %c%s\n", change, bit_desc[i]);
bit <<= 1;
i++;
}
}
I don't know if this is in any sort of fast-path or if
gcc will completely optimize this completely away if
pr_debug isn't declared, but maybe surround the function
implementation with
static void dump_port_status_diff(u32 prev_status, u32 new_status)
{
#ifdef DEBUG
...
#endif
}
next prev parent reply other threads:[~2011-06-13 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 21:30 [PATCH 2/3] usbip: dump the port status difference Németh Márton
2011-06-13 21:47 ` Németh Márton
2011-06-13 22:12 ` Joe Perches [this message]
2011-06-14 6:28 ` Németh Márton
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=1308003146.26699.43.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=max@hinterhof.net \
--cc=mfm@muteddisk.com \
--cc=nm127@freemail.hu \
--cc=sarah.a.sharp@linux.intel.com \
--cc=usbip-devel@lists.sourceforge.net \
/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