linux-kernel - Re: [RFC patch] init default dma_ops to prepare intel_iommu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3877989d0908130200k6d016a74w1947dc6bcd368a7f@mail.gmail.com>
Date:	Thu, 13 Aug 2009 17:00:38 +0800
From:	Luming Yu <luming.yu@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	fenghua.yu@...el.com, tony.luck@...el.com,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [RFC patch] init default dma_ops to prepare intel_iommu_init 
	failure

On Thu, Aug 13, 2009 at 4:49 PM, David Woodhouse<dwmw2@...radead.org> wrote:
> On Thu, 2009-08-13 at 16:11 +0800, Luming Yu wrote:
>> I treat this as -32 or -33 stuff, because I don't see a real system is blocking
>> on the problem. I found this problem when I was trying to disable some drhd
>> for debugging a real iommu issue...that one has priority.
>
> (The real bug you were chasing is fixed, isn't it? Or worked around, at
> least, since the BIOS in question is still closed source and broken.)

Yes the flood of dmar_fault on my HP compaq Dc7800u (my x86_64 linux
desktop) has been fixed. But I still have an iommu casued boot problem
on a ia64 box.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/