linux-kernel - Re: [RFC 1/3 v3] mm: iommu: An API to unify IOMMU, CPU and device memory management

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: <20100721072837.GB6009@n2100.arm.linux.org.uk>
Date:	Wed, 21 Jul 2010 08:28:37 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	"Shilimkar, Santosh" <santosh.shilimkar@...com>
Cc:	"stepanm@...eaurora.org" <stepanm@...eaurora.org>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"dwalker@...eaurora.org" <dwalker@...eaurora.org>,
	"mel@....ul.ie" <mel@....ul.ie>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	Zach Pfeffer <zpfeffer@...eaurora.org>,
	Michael Bohan <mbohan@...eaurora.org>,
	Tim HRM <zt.tmzt@...il.com>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"ebiederm@...ssion.com" <ebiederm@...ssion.com>
Subject: Re: [RFC 1/3 v3] mm: iommu: An API to unify IOMMU, CPU and device
	memory management

On Wed, Jul 21, 2010 at 11:19:58AM +0530, Shilimkar, Santosh wrote:
> > -----Original Message-----
> > From: linux-arm-kernel-bounces@...ts.infradead.org [mailto:linux-arm-
> > kernel-bounces@...ts.infradead.org] On Behalf Of Russell King - ARM Linux
> > Sent: Wednesday, July 21, 2010 4:00 AM
> > To: stepanm@...eaurora.org
> > Cc: linux-arch@...r.kernel.org; dwalker@...eaurora.org; mel@....ul.ie;
> > linux-arm-msm@...r.kernel.org; linux-kernel@...r.kernel.org; FUJITA
> > Tomonori; linux-mm@...ck.org; andi@...stfloor.org; Zach Pfeffer; Michael
> > Bohan; Tim HRM; linux-omap@...r.kernel.org; linux-arm-
> > kernel@...ts.infradead.org; ebiederm@...ssion.com
> > Subject: Re: [RFC 1/3 v3] mm: iommu: An API to unify IOMMU, CPU and device
> > memory management

*************************************************************************
> > This is difficult to achieve without remapping kernel memory using L2
> > page tables, so we can unmap pages on 4K page granularity.  That's
> > going to increase TLB overhead and result in lower system performance
> > as there'll be a greater number of MMU misses.
*************************************************************************

> > However, one obvious case would be to use highmem-only pages for
> > remapping - but you then have to ensure that those pages are never
> > kmapped in any way, because those mappings will fall into the same
> > unpredictable category that we're already trying to avoid.  This
> > may be possible, but you'll have to ensure that most of the system
> > RAM is in highmem - which poses other problems (eg, if lowmem gets
> > low.)
>
> Why can't we consider an option of removing the old mappings when 
> we need to create new ones with different attributes as suggested
> by Catalin on similar thread previously. This will avoid the duplicate
> mapping with different attributes issue on newer ARMs.

See the first paragraph which I've highlighted above.
--
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/