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
| ||
|
Date: Tue, 24 Mar 2020 08:54:02 +0100 From: Christoph Hellwig <hch@....de> To: Alexey Kardashevskiy <aik@...abs.ru> Cc: Christoph Hellwig <hch@....de>, "Aneesh Kumar K.V" <aneesh.kumar@...ux.ibm.com>, iommu@...ts.linux-foundation.org, linuxppc-dev@...ts.ozlabs.org, Lu Baolu <baolu.lu@...ux.intel.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Joerg Roedel <joro@...tes.org>, Robin Murphy <robin.murphy@....com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] dma-mapping: add a dma_ops_bypass flag to struct device On Tue, Mar 24, 2020 at 02:05:54PM +1100, Alexey Kardashevskiy wrote: > This is for persistent memory which you can DMA to/from but yet it does > not appear in the system as a normal memory and therefore requires > special handling anyway (O_DIRECT or DAX, I do not know the exact > mechanics). All other devices in the system should just run as usual, > i.e. use 1:1 mapping if possible. On other systems (x86 and arm) pmem as long as it is page backed does not require any special handling. This must be some weird way powerpc fucked up again, and I suspect you'll have to suffer from it.
Powered by blists - more mailing lists