linux-kernel - Re: [PATCH] x86: OLPC: add support for calling into OpenFirmware (v5)

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]

Date:	Fri, 18 Jun 2010 21:56:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Andres Salomon <dilinger@...ued.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	x86@...nel.org, Mitch Bradley <wmb@...top.org>
Subject: Re: [PATCH] x86: OLPC: add support for calling into OpenFirmware (v5)


* H. Peter Anvin <hpa@...or.com> wrote:

> On 06/18/2010 12:42 PM, Andres Salomon wrote:
> > +
> > +	/* install OFW's PDE permanently into the kernel's pgtable */
> > +	set_pgd(&swapper_pg_dir[OLPC_OFW_PDE_NR], *ofw_pde);
> > +	flush_tlb();
> > +	early_iounmap(base, sizeof(olpc_ofw_pgd) * PTRS_PER_PGD);
> 
> I just realized... this flush_tlb() is actually not necessary since on x86 
> it is always legal to go from a less permissive configuration to a more 
> permissive, and the initial configuration is "not present" which is 
> maximally nonpermissive.
> 
> Could you take it out and make sure it still works?

small nit: an optimization barrier would still be needed if the result is 
being relied on by the kernel.

Thanks,

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