From: Ingo Molnar <mingo@elte.hu>
To: David Woodhouse <dwmw2@infradead.org>
Cc: torvalds@linux-foundation.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT *] intel-iommu updates for 2.6.30 (second batch)
Date: Tue, 7 Apr 2009 07:52:45 +0200 [thread overview]
Message-ID: <20090407055245.GA10406@elte.hu> (raw)
In-Reply-To: <20090407054818.GA5557@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * David Woodhouse <dwmw2@infradead.org> wrote:
>
> > On Tue, 2009-04-07 at 07:37 +0200, Ingo Molnar wrote:
> > > I suspect these bits are the ones that broke the upstream build:
> > >
> > > drivers/pci/dmar.c:47: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> > > ‘__attribute__’ before ‘dmar_tbl_size’
> > > drivers/pci/dmar.c:62: warning: ‘struct acpi_dmar_device_scope’
> > > declared inside parameter list
> > > drivers/pci/dmar.c:62: warning: its scope is only this definition or
> > > declaration, which is probably not what you want
> >
> > Yeah, <acpi/acpi.h> was being included implicitly for me, but
> > certain configs don't do that. Alexander Beregalov sent a patch
> > for that, which I added to my tree before Linus pulled it.
> >
> > Commit 46f06b72378d3187f0d12f7a60d020676bfbf332 is the fix.
>
> No, that does not fix it - it's still broken with
> v2.6.29-9854-gd508afb. Try the config i sent.
The problem is INTR_REMAP. That brings in DMAR but not ACPI.
The patch below fixes it, but it is only an ugly workaround: we
really dont want 'depends on ACPI' dependencies to spread like that.
ACPI is a hardware discovery mechanism. It might be the only way to
discover these pieces of hardware at the moment, but we should not
tie method of discovery to hardware support. I'd suggest a
dmar_acpi.c splitout of the ACPI bits.
More testing too please - this was really an avoidable bug.
Ingo
---
arch/x86/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux2/arch/x86/Kconfig
===================================================================
--- linux2.orig/arch/x86/Kconfig
+++ linux2/arch/x86/Kconfig
@@ -268,7 +268,7 @@ config SMP_SUPPORT
config X86_X2APIC
bool "Support x2apic"
- depends on X86_LOCAL_APIC && X86_64
+ depends on X86_LOCAL_APIC && X86_64 && ACPI
select INTR_REMAP
---help---
This enables x2apic support on CPUs that have this feature.
next prev parent reply other threads:[~2009-04-07 5:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1238839639.3560.37.camel@macbook.infradead.org>
2009-04-07 5:37 ` [GIT *] intel-iommu updates for 2.6.30 (second batch) Ingo Molnar
2009-04-07 5:42 ` Ingo Molnar
2009-04-07 5:52 ` David Woodhouse
2009-04-07 5:44 ` David Woodhouse
2009-04-07 5:48 ` Ingo Molnar
2009-04-07 5:52 ` Ingo Molnar [this message]
2009-04-07 6:04 ` David Woodhouse
2009-04-07 6:15 ` Ingo Molnar
2009-04-07 6:18 ` David Woodhouse
2009-04-07 8:49 ` Ingo Molnar
2009-04-07 9:02 ` [PATCH] intel-iommu: fix build with CONFIG_BRANCH_TRACER=y Ingo Molnar
2009-04-07 11:33 ` David Woodhouse
2009-04-07 12:14 ` Ingo Molnar
2009-04-07 12:44 ` David Woodhouse
2009-04-07 12:57 ` Ingo Molnar
2009-04-07 13:14 ` David Woodhouse
2009-04-07 14:54 ` Linus Torvalds
2009-04-07 14:59 ` Linus Torvalds
2009-04-07 15:12 ` Ingo Molnar
[not found] ` <f73f7ab80904071540w3d298c3bh386b46d5685f746e@mail.gmail.com>
2009-04-07 22:42 ` Kyle Moffett
2009-04-07 14:50 ` Linus Torvalds
2009-04-07 6:39 ` [GIT *] intel-iommu updates for 2.6.30 (second batch) 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=20090407055245.GA10406@elte.hu \
--to=mingo@elte.hu \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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