From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: pci_iommu_init() crash
Date: Mon, 30 Aug 2010 10:32:06 -0400 [thread overview]
Message-ID: <20100830143206.GB5652@phenom.dumpdata.com> (raw)
In-Reply-To: <20100829173216.GA19896@elte.hu>
On Sun, Aug 29, 2010 at 07:32:16PM +0200, Ingo Molnar wrote:
>
> FYI, -tip testing found a new boot crash, caused by the new x86/iommu
> commits:
>
> 6f44d03: x86, doc: Adding comments about .iommu_table and its neighbors.
> ee1f284: x86, iommu: Utilize the IOMMU_INIT macros functionality.
> 4db77ff: x86, VT-d: Make Intel VT-d IOMMU use IOMMU_INIT_* macros.
> 22e6daf: x86, GART/AMD-VI: Make AMD GART and IOMMU use IOMMU_INIT_* macros.
> d2aa232: x86, calgary: Make Calgary IOMMU use IOMMU_INIT_* macros.
> 5cb3a26: x86, xen-swiotlb: Make Xen-SWIOTLB use IOMMU_INIT_* macros.
> c116c54: x86, swiotlb: Make SWIOTLB use IOMMU_INIT_* macros.
> efa631c: x86, swiotlb: Simplify SWIOTLB pci_swiotlb_detect routine.
> 5bef80a: x86, iommu: Add proper dependency sort routine (and sanity check).
> 480125b: x86, iommu: Make all IOMMU's detection routines return a value.
> 0444ad9: x86, iommu: Add IOMMU_INIT macros, .iommu_table section, and iommu_table_entry structure
>
> Crashlog is below, config attached. I've excluded x86/iommu from
> tip:master for now.
Fixing it right now. Thanks for the e-mail.
next prev parent reply other threads:[~2010-08-30 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 17:32 pci_iommu_init() crash Ingo Molnar
2010-08-30 14:32 ` Konrad Rzeszutek Wilk [this message]
2010-08-30 18:10 ` [PATCH] x86: Fix crash on X86 with IOMMU_INIT functinality Konrad Rzeszutek Wilk
2010-08-31 7:27 ` [tip:x86/iommu] x86, iommu: Fix IOMMU_INIT alignment rules tip-bot for Konrad Rzeszutek Wilk
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=20100830143206.GB5652@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.