From: Ingo Molnar <mingo@elte.hu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: dwmw2@infradead.org, torvalds@linux-foundation.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
tony.luck@intel.com
Subject: Re: [GIT *] iommu fixes for 2.6.28
Date: Fri, 24 Oct 2008 13:22:17 +0200 [thread overview]
Message-ID: <20081024112217.GA19266@elte.hu> (raw)
In-Reply-To: <20081024201041T.fujita.tomonori@lab.ntt.co.jp>
* FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> On Fri, 24 Oct 2008 13:01:25 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
>
> >
> > * David Woodhouse <dwmw2@infradead.org> wrote:
> >
> > > This contains a few iommu-related fixes -- it restores DMA remapping
> > > on newer Intel hardware, which was disabled by the interrupt remapping
> > > patches, adds IA64 support for the Intel IOMMU, and some other small
> > > fixes.
> > >
> > > MAINTAINERS | 7 +
> > > arch/x86/kernel/amd_iommu_init.c | 2 +-
> > > arch/x86/kernel/pci-dma.c | 16 ---
> > > drivers/pci/dmar.c | 119 +++++++++++++-----
> > > drivers/pci/intel-iommu.c | 250 ++++++++++++++++++++------------------
> > > drivers/pci/quirks.c | 14 ++
> > > include/asm-x86/iommu.h | 4 +
> > > include/linux/dma_remapping.h | 27 ++--
> > > include/linux/intel-iommu.h | 66 ++++++++---
> > > 9 files changed, 305 insertions(+), 200 deletions(-)
> >
> > hm, i just updated to v2.6.28-rc1, and these changes broke the x86
> > 32-bit build:
> >
> > arch/x86/kernel/built-in.o: In function `dma_supported':
> > (.text+0x5797): undefined reference to `forbid_dac'
> > arch/x86/kernel/built-in.o: In function `iommu_setup':
> > pci-dma.c:(.init.text+0x326c): undefined reference to `forbid_dac'
> > pci-dma.c:(.init.text+0x328b): undefined reference to `forbid_dac'
> > pci-dma.c:(.init.text+0x32aa): undefined reference to `forbid_dac'
> >
> > seems to be caused by:
> >
> > 5b6985c: intel-iommu: IA64 support
>
> http://marc.info/?l=linux-kernel&m=122480590627590&w=2
>
>
> Sharing forbid_dac between IA64 and X86 doesn't make sense and IA64
> doesn't even use forbid_dac... Reverting the forbid_dac relocation is
> the right fix, I think.
could you send a patch for it please? Commit 5b6985c does many things at
once so the revert is not trivial.
Ingo
next prev parent reply other threads:[~2008-10-24 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 19:14 [GIT *] iommu fixes for 2.6.28 David Woodhouse
2008-10-24 11:01 ` Ingo Molnar
2008-10-24 11:08 ` Ingo Molnar
2008-10-24 11:40 ` Ingo Molnar
2008-10-24 11:10 ` FUJITA Tomonori
2008-10-24 11:22 ` Ingo Molnar [this message]
2008-10-24 11:36 ` FUJITA Tomonori
2008-10-24 11:39 ` 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=20081024112217.GA19266@elte.hu \
--to=mingo@elte.hu \
--cc=dwmw2@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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