mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: I/O APIC: Always report how the timer has been set up
Date: Fri, 18 Jul 2008 14:22:27 +0200	[thread overview]
Message-ID: <20080718122227.GN6875@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.55.0807141845120.17431@cliff.in.clinika.pl>


* Maciej W. Rozycki <macro@linux-mips.org> wrote:

>  Following recent (and less so) issues with the 8254 timer when routed 
> through the I/O or local APIC, always report which configurations have 
> been tried and which one has been set up eventually.  This is so that 
> logs posted by people for some other reason can be used as a 
> cross-reference when investigating any possible future problems.
> 
>  The change unifies messages printed on 32-bit and 64-bit platforms 
> and adds trailing newlines (removes leading ones), so that proper log 
> level annotation can be used and any possible interspersed output will 
> not cause a mess.
> 
>  I have chosen to use apic_printk(APIC_QUIET, ...) rather than 
> printk(...) so that the distinction of these messages is maintained 
> making possible future decisions about changes in this area easier.  A 
> change posted separately making apic_verbosity unsigned removes any 
> extra code that would otherwise be generated as a result of this 
> design decision.
> 
> Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>

applied to tip/x86/apic, thanks Maciej.

ported this portion ontop of the write-around-removal patch:

>  	apic_write_around(APIC_LVT0, APIC_DM_FIXED | vector);	/* Fixed mode */
>  	enable_8259A_irq(0);
>  
>  	if (timer_irq_works()) {
> -		printk(" works.\n");
> +		apic_printk(APIC_QUIET, KERN_INFO "..... works.\n");
>  		goto out;
>  	}
>  	disable_8259A_irq(0);
>  	apic_write_around(APIC_LVT0, APIC_LVT_MASKED | APIC_DM_FIXED | vector);
> -	printk(" failed.\n");
> +	apic_printk(APIC_QUIET, KERN_INFO "..... failed.\n");
>  
> -	printk(KERN_INFO "...trying to set up timer as ExtINT IRQ...");
> +	apic_printk(APIC_QUIET, KERN_INFO
> +		    "...trying to set up timer as ExtINT IRQ...\n");
>  
>  	init_8259A(0);
>  	make_8259A_irq(0);

	Ingo

      reply	other threads:[~2008-07-18 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 18:08 Maciej W. Rozycki
2008-07-18 12:22 ` Ingo Molnar [this message]

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=20080718122227.GN6875@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®