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 Jan 2015 16:14:59 -0700 From: Ross Zwisler <ross.zwisler@...ux.intel.com> To: Borislav Petkov <bp@...en8.de> Cc: "H. Peter Anvin" <h.peter.anvin@...el.com>, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH v2 0/2] add support for new persistent memory instructions On Mon, 2015-01-26 at 23:39 +0100, Borislav Petkov wrote: > On Mon, Jan 26, 2015 at 02:50:07PM -0700, Ross Zwisler wrote: > > We can use MFENCE, but I don't think we need to. With SFENCE we will > > be ordered with respect to stores, and the flushes and pcommit will be > > ordered with respect to one another. I think you can sprinkle in loads > > anywhere you want in that flow and everything will work. > > > Ok, maybe we should hold down that sequence and this somewhere as a > this-is-how-you-should-do-pcommit-properly explanation or so... or do > you have an actual patch adding write_and_commit_buffer()? I don't have a patch to add and use this yet. I'll add the flow to the commit messages for both pcommit and clwb. -- 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