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: Mon, 26 Sep 2011 18:21:32 +0900 From: KyongHo Cho <pullip.cho@...sung.com> To: Ohad Ben-Cohen <ohad@...ery.com> Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-samsung-soc@...r.kernel.org" <linux-samsung-soc@...r.kernel.org>, "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "joerg.roedel@....com" <joerg.roedel@....com>, 이상현 <sanghyun75.lee@...sung.com>, 김국진 <kgene.kim@...sung.com>, 김영락 <younglak1004.kim@...sung.com> Subject: Re: [PATCH 3/4] iommu/exynos: Add iommu driver for Exynos4 Platforms On Mon, Sep 26, 2011 at 6:05 PM, Ohad Ben-Cohen <ohad@...ery.com> wrote: > On Mon, Sep 26, 2011 at 11:58 AM, KyongHo Cho <pullip.cho@...sung.com> wrote: >> As you've noticed, it is default behavior for iommu fault. > > Then why not add it to the IOMMU core ? it's quite generic and can be > useful for others, too. > Every fault in IOMMU (System MMU) is an error logically and must not happen in our multimedia device drivers because, our device drivers always construct page table completely before address translation in System MMU and TLB loads translation information automatically when TLB miss. I am not sure if the default behavior of MMU fault in our IOMMU driver is also correct for other IOMMU drivers. BTW, I think we need more fault type than IOMMU_FAULT_READ and IOMMU_FAULT_WRITE. We have page fault, access fault(read, write), security fault and bus error (translated physical address is not available) > Thanks, > Ohad. Thank you. Cho KyongHo. -- 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