linux-kernel - RE: [PATCH v6 1/9] efi: Use early_mem*() instead of early

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] [day] [month] [year] [list]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F32846B97@ORSMSX114.amr.corp.intel.com>
Date:	Tue, 24 Jun 2014 17:56:09 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Daniel Kiper <daniel.kiper@...cle.com>,
	Jan Beulich <JBeulich@...e.com>
CC:	"andrew.cooper3@...rix.com" <andrew.cooper3@...rix.com>,
	"david.vrabel@...rix.com" <david.vrabel@...rix.com>,
	"ian.campbell@...rix.com" <ian.campbell@...rix.com>,
	"stefano.stabellini@...citrix.com" <stefano.stabellini@...citrix.com>,
	"jeremy@...p.org" <jeremy@...p.org>,
	"Fleming, Matt" <matt.fleming@...el.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
	"boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
	"konrad.wilk@...cle.com" <konrad.wilk@...cle.com>,
	"eshelton@...ox.com" <eshelton@...ox.com>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"mjg59@...f.ucam.org" <mjg59@...f.ucam.org>,
	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"hpa@...or.com" <hpa@...or.com>,
	"Yu, Fenghua" <fenghua.yu@...el.com>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>
Subject: RE: [PATCH v6 1/9] efi: Use early_mem*() instead of early_io*()

> I am CC'ing IA-64 guys.

The *_unmap() functions are no-op on ia64 - because we have mappings for everything all the time
- the *_map() functions just need to compute the proper address to use to get the right attributes
(so we don't mix and match cacheable and uncachable access to the same address). But there is
nothing to tear down afterwards.

I do tend to agree with Daniel that is seems odd to setup the mapping with one class of function
and then tear it down with another.

-Tony

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