Suspend or kill a syscall in hypervisor

Suspend or kill a syscall in hypervisor

[Carlo Maiero]

[-- Attachment #1.1: Type: text/plain, Size: 288 bytes --]

I've made a patch that intercept some type of (malicious) hypercall and
syscall of domU in the hypervisor,
and handle the log in the dom0.

How can i suspend or kill a certain syscall (or hypercall) on a vcpu?
The easy way is to suspend the virtual machine, but i think it's
unnecessary.

[-- Attachment #1.2: Type: text/html, Size: 520 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Suspend or kill a syscall in hypervisor

[Carlo Maiero]

[-- Attachment #1.1: Type: text/plain, Size: 687 bytes --]

2010/10/4 Carlo Maiero <zesster@gmail.com>

> I've made a patch that intercept some type of (malicious) hypercall and
> syscall of domU in the hypervisor,
> and handle the log in the dom0.
>
> How can i suspend or kill a certain syscall (or hypercall) on a vcpu?
> The easy way is to suspend the virtual machine, but i think it's
> unnecessary.
>
>
To block the instruction, i think i've to clear vcpu register and skip  to
the next instruction, or set failure result in a register.

To stop the execution of the process i've to call a function in traps.c i
think near line 400.
This function will wait for a value to be 1.

Which is the best way to implement a semaphore at this level?

[-- Attachment #1.2: Type: text/html, Size: 1173 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel