Ingo Molnar wrote: > ok, i changed this and i added the SVM patch function too. AMD's VMMCALL > is 0x0f, 0x01, 0xd9, correct? > > yes.
>> Where is the vmcall exit handler? >> > > in my tree, have not sent the patch yet - first want to combine it with > the cr3 feature to have it tested. > > I'd like it in the final patch. btw, we need to define the hypercall protocol. We should aim for most things (esp. hypercall number and return code) to be passed in registers. Need to take care of 32/64 bit compatibility from day one. Patches look good. Only thing missing is printk() log levels. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
