From: Ingo Molnar <mingo@elte.hu>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
ak@suse.de, linux-kernel@vger.kernel.org, nanhai.zou@intel.com,
asit.k.mallick@intel.com, keith.packard@intel.com,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v2)
Date: Thu, 31 May 2007 15:34:26 +0200 [thread overview]
Message-ID: <20070531133426.GA30616@elte.hu> (raw)
In-Reply-To: <m1d50h5irm.fsf@ebiederm.dsl.xmission.com>
looks good to me:
Acked-by: Ingo Molnar <mingo@elte.hu>
with a few minor style nits:
> +static int io_apic_level_ack_pending(unsigned int irq)
> +{
> + struct irq_pin_list *entry;
> + unsigned long flags;
> + int pending = 0;
> + spin_lock_irqsave(&ioapic_lock, flags);
newline after variable sections please.
> + entry = irq_2_pin + irq;
> + for (;;) {
> + unsigned int reg;
> + int pin;
> + pin = entry->pin;
ditto.
> + if (pin == -1)
> + break;
> + reg = io_apic_read(entry->apic, 0x10 + pin*2);
> + /* Is the remote IRR bit set? */
> + pending |= (reg >> 14) & 1;
> + if (!entry->next)
> + break;
> + entry = irq_2_pin + entry->next;
> + }
> + spin_unlock_irqrestore(&ioapic_lock, flags);
> + return pending;
optional: it looks a bit better with a newline before the 'return'
statement.
> +}
> +
> +
and here there's one too much newline :-)
Ingo
next prev parent reply other threads:[~2007-05-31 13:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 23:03 [patch] x86_64, irq: check remote IRR bit before migrating level triggered irq Siddha, Suresh B
2007-05-17 23:58 ` Eric W. Biederman
2007-05-18 0:43 ` Siddha, Suresh B
2007-05-18 0:30 ` Eric W. Biederman
2007-05-18 1:01 ` Siddha, Suresh B
2007-05-18 14:40 ` Eric W. Biederman
2007-05-18 17:30 ` Yinghai Lu
2007-05-18 18:01 ` Eric W. Biederman
2007-05-18 18:09 ` Yinghai Lu
2007-05-18 18:20 ` Eric W. Biederman
2007-05-18 18:07 ` Siddha, Suresh B
2007-05-18 18:28 ` Yinghai Lu
2007-05-18 18:39 ` Siddha, Suresh B
2007-05-18 19:02 ` Eric W. Biederman
2007-05-18 19:18 ` Siddha, Suresh B
2007-05-31 2:50 ` Eric W. Biederman
2007-05-18 12:00 ` Andi Kleen
2007-05-18 14:19 ` Eric W. Biederman
2007-05-31 11:34 ` [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v2) Eric W. Biederman
2007-05-31 12:01 ` Andi Kleen
2007-05-31 13:29 ` Eric W. Biederman
2007-05-31 20:02 ` Siddha, Suresh B
2007-05-31 13:34 ` Ingo Molnar [this message]
2007-05-31 13:50 ` [PATCH] x86_64 irq: check remote IRR bit before migrating level triggered irq (v3) Eric W. Biederman
2007-05-31 13:54 ` Ingo Molnar
2007-05-31 20:00 ` Siddha, Suresh B
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=20070531133426.GA30616@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=asit.k.mallick@intel.com \
--cc=ebiederm@xmission.com \
--cc=keith.packard@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=yhlu.kernel@gmail.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
Powered by JetHome