mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	Jeff Garzik <jgarzik@pobox.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	asit.k.mallick@intel.com, Andi Kleen <ak@suse.de>
Subject: Re: [Patch 0/2] Disable SW irqbalance/irqaffinity for E7520/E7320/E7525
Date: Mon, 27 Sep 2004 11:03:51 -0700	[thread overview]
Message-ID: <20040927110350.C18131@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0409251206120.2914@musoma.fsmlabs.com>; from zwane@linuxpower.ca on Sat, Sep 25, 2004 at 12:15:27PM +0300

Zwane,

As far as irq_affinity is concerned, workaround fits nicely in quirks.c
infrastructure.

x86 irqbalance is the one which is causing the pain. Workaround will be more
cleaner if we can move balanced_irq_init() to late_initcall.

If there is no objection, I can post a new patch with that change.

thanks,
suresh

On Sat, Sep 25, 2004 at 12:15:27PM +0300, Zwane Mwaikambo wrote:
> On Fri, 24 Sep 2004, Suresh Siddha wrote:
> > +#ifdef CONFIG_X86_IO_APIC
> > +#include <asm/hw_irq.h>
> > +#ifdef CONFIG_IRQBALANCE
> > +extern int irqbalance_disable(char *str);
> > +#endif
> > +extern int no_irq_affinity;
> > +extern int noirqdebug_setup(char *str);
> 
> Ok this is sort of ugly, but it's not your fault, i understand that the
> PCI quirks code is too late after IOAPIC setup, x86_64 has some early PCI
> bridge detection code which helps in doing IOAPIC quirks.
> 
> > +void __devinit quirk_intel_irqbalance(struct pci_dev *dev)
> 
> This may as well be moved elsewhere since it's not actually going to be 
> used in PCI quirks. I think you should just do the chipset detection in 
> io_apic.c and then do the disable from there, it's racy and strange 
> (although it may seem natural) to do it in quirks.c

  reply	other threads:[~2004-09-27 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  6:34 Suresh Siddha
2004-09-24 15:05 ` Zwane Mwaikambo
2004-09-24 20:24   ` Jeff Garzik
2004-09-24 22:20     ` Suresh Siddha
2004-09-25  9:15       ` Zwane Mwaikambo
2004-09-27 18:03         ` Suresh Siddha [this message]
2004-09-28 21:11           ` Suresh Siddha
2004-09-29 15:16             ` Zwane Mwaikambo
2004-09-30 22:51             ` Andrew Morton
2004-10-01  1:15               ` Suresh Siddha
2004-09-29 13:36           ` Zwane Mwaikambo

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=20040927110350.C18131@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=asit.k.mallick@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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