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,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] x86: Recover timer_ack lost in the merge of the NMI watchdog
Date: Sun, 13 Jul 2008 11:44:34 +0200	[thread overview]
Message-ID: <20080713094434.GA32578@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.55.0807130339010.6739@cliff.in.clinika.pl>


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

> On Fri, 11 Jul 2008, Ingo Molnar wrote:
> 
> > i've applied your fixes to tip/x86/core:
> > 
> >  Maciej W. Rozycki (4):
> >       x86: L-APIC: Set IRQ0 as edge-triggered
> >       x86: L-APIC: Always fully configure IRQ0
> >       x86: I/O APIC: Never configure IRQ2
> >       x86: Recover timer_ack lost in the merge of the NMI watchdog
> 
> Thanks, please apply "x86: I/O APIC: Remove an IRQ2-mask hack" on top 
> of these.  Then what currently comprises 
> dmi_ignore_irq0_timer_override() can be done more properly as soon as 
> we know how to get information about INTIN0/2 configurations from the 
> SB400.  Furthermore, following considerations in the other mail, I 
> think the HPET driver should use the notion of ISA IRQ numbers by 
> mapping them appropriately from I/O APIC pin numbers.  Reusing 
> pin_2_irq() for this purpose seems a reasonable way of doing this to 
> me.

applied to tip/x86/core, thanks Maciej.

	Ingo

      reply	other threads:[~2008-07-13  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11 18:47 Maciej W. Rozycki
2008-07-11 18:55 ` Ingo Molnar
2008-07-13  2:58   ` Maciej W. Rozycki
2008-07-13  9:44     ` 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=20080713094434.GA32578@elte.hu \
    --to=mingo@elte.hu \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=rjw@sisk.pl \
    --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®