I can start working on either of them, but I don't want to do
something someone else is already doing or get in the way of the
refactoring that's been going on. If someone gives me the OK, I'll
take a shot at implementation and post a patch to the issue for
review.
-jon
Currently we are still finishing to refactor the code to make it "100%
VMX-independent", so that if someone wants to add the support for SVM, he
doesn't need to modify all the modules. In a couple of days we plan to start to
include the support for PAE. I don't think it will take too much time.
> I can start working on either of them, but I don't want to do
> something someone else is already doing or get in the way of the
> refactoring that's been going on. If someone gives me the OK, I'll
> take a shot at implementation and post a patch to the issue for
> review.
Another important issue with HyperDbg is that currently it doesn't support USB
keyboards. Unfortunately, many recent desktop PCs don't provide a PS/2
interface, so HyperDbg is pretty useless on them. I think it will be very nice
to have a (minimalistic) HVM-level driver to handle USB keyboards. Moreover,
the development of such a module won't interfere with the refactoring that is
going on.
What do you think about this?
> Another important issue with HyperDbg is that currently it doesn't support USB
> keyboards. Unfortunately, many recent desktop PCs don't provide a PS/2
> interface, so HyperDbg is pretty useless on them. I think it will be very nice
> to have a (minimalistic) HVM-level driver to handle USB keyboards. Moreover,
> the development of such a module won't interfere with the refactoring that is
> going on.
>
> What do you think about this?
>
Cool, I'll look into this.
-jon