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]
Date:	Wed, 25 Nov 2009 01:45:10 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip] x86: fix iommu=soft boot option

Ingo Molnar wrote:
> * FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:
> 
>> On Wed, 25 Nov 2009 00:54:34 -0800
>> Yinghai Lu <yinghai@...nel.org> wrote:
>>
>>> only remember that SLES 9 SP3 (?) at some point has problem with AMD 
>>> 10h ( quad core version) when memory > 4 g (with USB controller ?) 
>>> because the gart code only check K8 device id, and didn't check 10h 
>>> device id. so gart iommu is not used. and happenly swiotlb code has 
>>> problem with that kernel version.
>>>
>>> thinking we should keep old behavior, until some day we can remove 
>>> them all.
>> Why? We are talking about changing 2.6.33 behavior. swiotlb in 2.6.33 
>> should be the safe option.
> 
> If that behavior was relied on for suspected (or real) bugs in the 
> swiotlb code then i agree that we should do this change. (and fix any 
> bugs if they still occur.)

after look at gart_iommu_hole_init() closely,

should be

for AMD 64bit, MEM > 4g, no AGP, iommu=soft
1. if BIOS have correct gart setting, Kernel will use swiotlb
2. if BIOS does not have correct gart setting, Kernel will use swiotlb

and for the all the cases, the codes after that 
/* Fix up the north bridges */
...

will disable the translation...

so even swiotlb=soft is used, gart_iommu_hole_init() still need to be called. to make sure aperture is disabled somehow.

YH
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ