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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 19 Mar 2007 13:47:49 +1100 From: Rusty Russell <rusty@...tcorp.com.au> To: Andi Kleen <ak@....de> Cc: David Miller <davem@...emloft.net>, jeremy@...p.org, mingo@...e.hu, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com, chrisw@...s-sol.org, zach@...are.com, anthony@...emonkey.ws, torvalds@...ux-foundation.org, netdev@...r.kernel.org Subject: Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable On Sun, 2007-03-18 at 13:08 +0100, Andi Kleen wrote: > > The idea is _NOT_ that you go look for references to the paravirt_ops > > members structure, that would be stupid and you wouldn't be able to > > use the most efficient addressing mode on a given cpu, you'd be > > patching up indirect calls and crap like that. Just say no... > > That wouldn't handle inlines though. At least some of the current > paravirtops like cli/sti are critical enough to require inlining. Well, we'd patch the inline over the call if we have room. Magic patching would be neat, but the downsides are that (1) we can't expand the patching room and (2) there's no way of attaching clobber info to the call site (doing register liveness analysis is not appealing). Now, this may not be fatal. 5 bytes is enough for all the native ops to be patched inline. For lguest this covers popf and pushf, but not cli and sti (10 bytes): they'd have to be calls. As for clobber info, it turns out that almost all of the calls can clobber %eax, which is probably enough. We just need to mark the handful of asm ones where this isn't true. Thoughts? Rusty. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists