| 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
| ||
|
Message-ID: <Pine.LNX.4.64.0608021821350.26404@schroedinger.engr.sgi.com> Date: Wed, 2 Aug 2006 18:25:09 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Zachary Amsden <zach@...are.com> cc: Jeremy Fitzhardinge <jeremy@...p.org>, Jeremy Fitzhardinge <jeremy@...source.com>, akpm@...l.org, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com, Ian Pratt <ian.pratt@...source.com>, Christian Limpach <Christian.Limpach@...cam.ac.uk>, Chris Wright <chrisw@...s-sol.org> Subject: Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor. On Wed, 2 Aug 2006, Zachary Amsden wrote: > It needn't be all architectures yet - only architectures that want to compile > Xen drivers are really affected. Perhaps a better place for these locking > primitives is in a Xen-specific driver header which defines appropriate > primitives for the architectures required? Last I remember, there were still > some issues here where atomic partial word operations couldn't be supported on > some architectures. Good idea. This will also make it easier to support this special functionality. And it will avoid use in contexts where these are not necessary. - 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