| 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: Sat, 15 Sep 2007 12:35:02 +1000 From: Rusty Russell <rusty@...tcorp.com.au> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: Anthony Liguori <aliguori@...ibm.com>, kvm-devel@...ts.sourceforge.net, Avi Kivity <avi@...ranet.com>, Ingo Molnar <mingo@...e.hu>, Dor Laor <dor.laor@...ranet.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Refactor hypercall infrastructure On Fri, 2007-09-14 at 13:53 -0700, Jeremy Fitzhardinge wrote: > Anthony Liguori wrote: > > This patch refactors the current hypercall infrastructure to better support live > > migration and SMP. It eliminates the hypercall page by trapping the UD > > exception that would occur if you used the wrong hypercall instruction for the > > underlying architecture and replacing it with the right one lazily. > > > > I guess it would be pretty rude/unlikely for these opcodes to get reused > in other implementations... But couldn't you make the page trap > instead, rather than relying on an instruction fault? That's a pain for inline hypercalls tho. I was planning on moving lguest to this model (which is interesting, because AFAICT this insn will cause a #UD or #GP depending on whether VT is supported on this box so I have to look for both). Cheers, Rusty. - 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