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: <3877989d0908121924t1589941fmcd45d3669b78bba4@mail.gmail.com>
Date:	Thu, 13 Aug 2009 10:24:20 +0800
From:	Luming Yu <luming.yu@...il.com>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	dwmw2@...radead.org, 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 10:11 AM, FUJITA
Tomonori<fujita.tomonori@....ntt.co.jp> wrote:
> On Wed, 12 Aug 2009 17:20:11 +0800
> Luming Yu <luming.yu@...il.com> wrote:
>
>> Hi there,
>>
>> On ia64 platform with dmar table and new upstream
>> kernel(config_dmar_default_on enabled),
>> if intel_iommu_init ends up without dma_ops initialized or other iommu
>> failures.
>> We got nothing to fall back. The following patch fixes it.
>
> Hmm, I think that the current code should work.

Without the patch, I encounters boot failure with the following .config

162-CONFIG_IA64_GENERIC=y
163-# CONFIG_IA64_DIG is not set
164:# CONFIG_IA64_DIG_VTD is not set

> Note that IA64_DIG_VTD doesn't enable SWIOTLB so there is fall
> back. That's kinda the IA64 policy about non IA64_GENERIC kernel.
>
how comes?
--
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/