From: Ingo Molnar <mingo@elte.hu>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "Kay, Allen M" <allen.m.kay@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'iommu@lists.linux-foundation.org'"
<iommu@lists.linux-foundation.org>,
"'David Woodhouse'" <dwmw2@infradead.org>
Subject: Re: [PATCH 0/5] fix bugs of x2apic/intr-remap
Date: Sat, 18 Apr 2009 08:41:19 +0200 [thread overview]
Message-ID: <20090418064119.GA9287@elte.hu> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C01A6B7F4B3@pdsmsx503.ccr.corp.intel.com>
* Han, Weidong <weidong.han@intel.com> wrote:
> Ingo Molnar wrote:
> > Note, there's a new compiler warning caused by your patches:
> >
> > arch/x86/kernel/apic/io_apic.c:2543: warning: 'eoi_ioapic_irq'
> > defined but not used
> >
> > most likely by:
> >
> > 631dd75: x86, intr-remap: fix ack for interrupt remapping
> >
> > Ingo
>
> eoi_ioapic_irq is only used for remapped interrupt, so we should
> define eoi_ioapic_irq and __eoi_ioapic_irq when #ifdef
> CONFIG_INTR_REMAP.
Ok - please send a patch that fixes this.
Btw., it would be nice to reduce the number of #ifdef
CONFIG_INTR_REMAP's in all .c files in general - or even eliminate
them.
It might be feasible to move all the INTR_REMAP code into a separate
.c file and only build it in the INTR_REMAP case. I have not tried
to do that so i dont know - if the interfaces are too wide and
unnatural to the rest of the ioapic code it might not improve the
end result - but good layering generally does do the trick.
Ingo
next prev parent reply other threads:[~2009-04-18 6:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 8:42 Weidong Han
2009-04-17 8:42 ` [PATCH 1/5] docs: add nox2apic back to kernel-parameters.txt Weidong Han
2009-04-17 13:51 ` Ingo Molnar
2009-04-17 14:48 ` [tip:x86/apic] docs, x86: " tip-bot for Weidong Han
2009-04-18 7:31 ` [tip:x86/urgent] " tip-bot for Weidong Han
2009-04-19 8:24 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 2/5] x86,intr-remap: fix ack for interrupt remapping Weidong Han
2009-04-17 14:49 ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 3/5] x86, intr-remap: enable interrupt remapping early Weidong Han
2009-04-17 14:13 ` Ingo Molnar
2009-04-17 23:42 ` Suresh Siddha
2009-04-18 7:24 ` Ingo Molnar
2009-04-17 14:49 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 4/5] x86, intr-remap: add option to disable interrupt remapping Weidong Han
2009-04-17 14:49 ` [tip:x86/apic] " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 8:42 ` [PATCH 5/5] x86: fix x2apic/intr-remap resume Weidong Han
2009-04-17 14:15 ` Ingo Molnar
2009-04-17 14:49 ` [tip:x86/apic] x86, intr-remap: " tip-bot for Weidong Han
2009-04-19 8:25 ` tip-bot for Weidong Han
2009-04-17 14:30 ` [PATCH 0/5] fix bugs of x2apic/intr-remap Ingo Molnar
2009-04-17 14:41 ` Ingo Molnar
2009-04-18 3:07 ` Han, Weidong
2009-04-18 6:41 ` Ingo Molnar [this message]
2009-04-19 6:32 ` David Woodhouse
2009-04-19 8:22 ` Ingo Molnar
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=20090418064119.GA9287@elte.hu \
--to=mingo@elte.hu \
--cc=allen.m.kay@intel.com \
--cc=dwmw2@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=weidong.han@intel.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
all inboxes | Powered by JetHome®