From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH 2/4] x86: misc printk() adjustments
Date: Mon, 21 Dec 2015 14:41:47 +0000 [thread overview]
Message-ID: <56780FAB.4080307@citrix.com> (raw)
In-Reply-To: <56781BFA02000078000C1ECD@prv-mh.provo.novell.com>
On 21/12/15 14:34, Jan Beulich wrote:
> --- a/xen/arch/x86/io_apic.c
> +++ b/xen/arch/x86/io_apic.c
> @@ -2310,13 +2310,14 @@ int ioapic_guest_read(unsigned long phys
> return 0;
> }
>
> -#define WARN_BOGUS_WRITE(f, a...) \
> - dprintk(XENLOG_INFO, "\n%s: " \
> - "apic=%d, pin=%d, irq=%d\n" \
> - "%s: new_entry=%08x\n" \
> - "%s: " f, __FUNCTION__, apic, pin, irq, \
> - __FUNCTION__, *(u32 *)&rte, \
> - __FUNCTION__ , ##a )
> +#define WARN_BOGUS_WRITE(f, a...) \
> + dprintk(XENLOG_INFO, "\n" \
> + XENLOG_INFO "%s: apic=%d, pin=%d, irq=%d\n" \
> + XENLOG_INFO "%s: new_entry=%08x\n" \
> + XENLOG_INFO "%s: " f "\n", \
> + __func__, apic, pin, irq, \
> + __func__, *(u32 *)&rte, \
> + __func__, ##a )
>
> int ioapic_guest_write(unsigned long physbase, unsigned int reg, u32 val)
> {
> @@ -2388,7 +2389,7 @@ int ioapic_guest_write(unsigned long phy
> rte.vector = desc->arch.vector;
> if ( *(u32*)&rte != ret )
> WARN_BOGUS_WRITE("old_entry=%08x pirq=%d\n%s: "
> - "Attempt to modify IO-APIC pin for in-use IRQ!\n",
> + "Attempt to modify IO-APIC pin for in-use IRQ!",
> ret, pirq, __FUNCTION__);
Given that this is the sole user of WARN_BOGUS_WRITE(), I would
recommend folding it all together in a simple dprintk(), and remove some
of the redundant information, and fixing the resulting message to take
up fewer lines.
~Andrew
next prev parent reply other threads:[~2015-12-21 14:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 14:28 [PATCH 0/4] XSA-169 follow-up Jan Beulich
2015-12-21 14:33 ` [PATCH 1/4] arm: add missing newlines to printk()s Jan Beulich
2015-12-21 15:16 ` Stefano Stabellini
2015-12-21 14:34 ` [PATCH 2/4] x86: misc printk() adjustments Jan Beulich
2015-12-21 14:41 ` Andrew Cooper [this message]
2015-12-21 14:48 ` Jan Beulich
2015-12-22 11:48 ` Andrew Cooper
2015-12-21 14:35 ` [PATCH 3/4] VT-d: unhide messages needed for diagnosing firmware issues Jan Beulich
2015-12-22 1:33 ` Wu, Feng
2015-12-21 14:35 ` [PATCH 4/4] IOMMU: unhide messages useful for diagnostics Jan Beulich
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=56780FAB.4080307@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.