xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: IO-APIC: tweak debug key info formatting
Date: Fri, 3 Feb 2012 13:49:18 +0000	[thread overview]
Message-ID: <4F2BE5DE.6060908@citrix.com> (raw)
In-Reply-To: <4F2BF2C80200007800070EDD@nat28.tlf.novell.com>

On 03/02/12 13:44, Jan Beulich wrote:
>>>> On 03.02.12 at 14:30, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> Furthermore, printing fewer characters makes it less likely that the
>> serial buffer will overflow resulting in loss of critical debugging
>> information.
> For that part, shortening some of the strings would certainly be
> desirable too (delivery_mode being the worst).

I was considering that as well, but just wanted to get the alignment
issue sorted first.  I will respin the patch with much shorter lines.

>> --- a/xen/arch/x86/io_apic.c
>> +++ b/xen/arch/x86/io_apic.c
>> @@ -2406,13 +2406,13 @@ void dump_ioapic_irq_info(void)
>>             *(((int *)&rte) + 1) = io_apic_read(entry->apic, 0x11 + 2 * pin);
>>             spin_unlock_irqrestore(&ioapic_lock, flags);
>>
>> -            printk("vector=%u, delivery_mode=%u, dest_mode=%s, "
>> -                   "delivery_status=%d, polarity=%d, irr=%d, "
>> -                   "trigger=%s, mask=%d, dest_id:%d\n",
>> +            printk("vector=%3u delivery_mode=%u dest_mode=%s "
> Could you please print the vector as %02x instead? We should really
> do this consistently everywhere, and vectors in decimal are pretty
> meaningless anyway (as one will always need to convert them for
> purposes of priority determination or comparison with #define-s in
> the sources).

Very true - I agree as well.

> Jan
>
>> +                   "delivery_status=%d polarity=%d irr=%d "
>> +                   "trigger=%s mask=%d dest_id:%d\n",
>>                    rte.vector, rte.delivery_mode,
>> -                   rte.dest_mode ? "logical" : "physical",
>> +                   rte.dest_mode ? "logical " : "physical",
>>                    rte.delivery_status, rte.polarity, rte.irr,
>> -                   rte.trigger ? "level" : "edge", rte.mask,
>> +                   rte.trigger ? "level" : "edge ", rte.mask,
>>                    rte.dest.logical.logical_dest);
>>
>>             if ( entry->next == 0 )
>

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

  reply	other threads:[~2012-02-03 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 13:30 IO-APIC: tweak debug key info formatting Andrew Cooper
2012-02-03 13:44 ` Jan Beulich
2012-02-03 13:49   ` Andrew Cooper [this message]
2012-02-03 16:36     ` IO-APIC: tweak debug key info formatting v2 Andrew Cooper

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=4F2BE5DE.6060908@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir.xen@gmail.com \
    --cc=xen-devel@lists.xensource.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).