linux-kernel - Re: [Patch v4 0/9] *** Fix kdump failure in system with amd 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: <20160525070203.GA3198@x1.redhat.com>
Date:	Wed, 25 May 2016 15:02:03 +0800
From:	Baoquan He <bhe@...hat.com>
To:	joro@...tes.org
Cc:	iommu@...ts.linux-foundation.org, vincent.wan@....com,
	xlpang@...hat.com, dyoung@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [Patch v4 0/9] *** Fix kdump failure in system with amd iommu***

Hi Joerg,

Attachments are console log of normal kernel and kdump kernel on a test
machine at my hand, and the related information of lspci -vt and lspci
-vvv. Before I tried to defer the calling of set_dte_entry() until the
device driver try to call __map_single() to really allocate coherent
memory or do the mapping, seems it didn't work. I am surprised by the
simplicity and effectiveness of Intel IOMMU fix, but can't think of
where I have missed. 





View attachment "lspci-vt.log" of type "text/plain" (2277 bytes)

View attachment "lspci-vvv.log" of type "text/plain" (0 bytes)

View attachment "amd_iommu.log" of type "text/plain" (136033 bytes)