[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Suspend or kill a syscall in hypervisor


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Carlo Maiero <zesster@xxxxxxxxx>
  • Date: Wed, 6 Oct 2010 18:10:17 +0200
  • Delivery-date: Wed, 06 Oct 2010 09:11:18 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=N7fYYC/6K9tKLAu1thboVBESYv1fki7bMFj8SGcC+nB3H17GTW0wSVdezsSHEJcUIL myBmXw1MBOa+uo/jfEj+Q9YmicKrt2d6c2tcbT5U0l1PsBJQ4VbLjMYt8XC1ycF36zk4 svRyL/kswM4SEvUuTE75OG9943h8aweHbwBZA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

2010/10/4 Carlo Maiero <zesster@xxxxxxxxx>
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?

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.