public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] bug in irq_affinity_write_proc
Date: Mon, 26 Jul 2004 23:39:12 +0000	[thread overview]
Message-ID: <16645.38432.152087.784787@napali.hpl.hp.com> (raw)
In-Reply-To: <40FE2EBE.4070007@jp.fujitsu.com>

>>>>> On Mon, 26 Jul 2004 12:25:44 +0900, Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> said:

  >> How about using a bitset for pending_irq_redir?  Or at least a
  >> byte-array instead of a word-array.

  Kenji> I modified my patch to use bitset for pending_irq_redir.
  Kenji> Please take a look.

OK, I checked that in now, with an additional small change which I
think improves readability a bit (see below).

Thanks,

	--david

--
diff -Nru a/arch/ia64/kernel/irq.c b/arch/ia64/kernel/irq.c
--- a/arch/ia64/kernel/irq.c	2004-07-26 16:37:58 -07:00
+++ b/arch/ia64/kernel/irq.c	2004-07-26 16:37:58 -07:00
@@ -1029,12 +1029,13 @@
 	/* note - we hold desc->lock */
 	cpumask_t tmp;
 	irq_desc_t *desc = irq_descp(irq);
-	int irq_with_redir = test_bit(irq, pending_irq_redir) ? (irq | IA64_IRQ_REDIRECTED) : irq;
+	int redir = test_bit(irq, pending_irq_redir);
 
 	if (!cpus_empty(pending_irq_cpumask[irq])) {
 		cpus_and(tmp, pending_irq_cpumask[irq], cpu_online_map);
 		if (unlikely(!cpus_empty(tmp))) {
-			desc->handler->set_affinity(irq_with_redir, pending_irq_cpumask[irq]);
+			desc->handler->set_affinity(irq | (redir ? IA64_IRQ_REDIRECTED : 0),
+						    pending_irq_cpumask[irq]);
 		}
 		cpus_clear(pending_irq_cpumask[irq]);
 	}

      parent reply	other threads:[~2004-07-26 23:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  8:52 [PATCH] bug in irq_affinity_write_proc Kenji Kaneshige
2004-07-23 20:11 ` David Mosberger
2004-07-26  3:25 ` Kenji Kaneshige
2004-07-26 23:39 ` David Mosberger [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=16645.38432.152087.784787@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.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