This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Suspend or kill a syscall in hypervisor
From: Carlo Maiero <zesster@xxxxxxxxx>
Date: Wed, 6 Oct 2010 18:10:17 +0200
Delivery-date: Wed, 06 Oct 2010 09:11:18 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=6pS5+4kABUOeBFhoWz5aUzZOMfUTLfDW2gBEgfjbzxU=; b=CWNtYIR8KMubuk87t5xwM1ni56BoCvM9CS13qXF9ViY1pnvgDfxaBV4WZzkDeZ7xZY 6HP2uzhpLkCFMPW2wEyzdHYxlw6CrmjevBOr4jythzDqtC50oRzWOuHMiYon+GHh9Eox eDNr256pCa3+XJEtWM3VMcWB+hIN4wazivOYU=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTikDtHUpvudhHbAKH=VMWTCDaAe013kk=GqZODQv@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTikDtHUpvudhHbAKH=VMWTCDaAe013kk=GqZODQv@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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
<Prev in Thread] Current Thread [Next in Thread>