WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] vcpu_info

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] vcpu_info
From: "pallavi jk" <pallutai@xxxxxxxxx>
Date: Fri, 10 Oct 2008 23:29:05 +0530
Cc: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 10 Oct 2008 10:59:34 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=XJfq1XyJ8wZ4tCuQ/P6Ulkyj0ZLuVZL4k0SFAjvSC3k=; b=swRugRYrgdRlcOEvBwxWAmCuX18CO5DVrpncT7OTGh0mn2Mjj1KnKpYRKQU7t2fRFD Wqq62anf9NMB+3k/ZICp8LfyZqXY2DhaH60fM8reIPPby2n/0dH4KFuiOXjpXBdN1SRa cO8Xj3sk23/Qn4fJkX7krGZVUiiezqnDqAbyM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=Ki1FXPS/wVLYxb33lER9Gumq8CryepzxDZ95S6wg32oGRm7haSauHF+X6yrWgk8uDB 5j+pjYmKCj4CGKxjYmCGQWXQoi+DP9VXTGERT64FHLbBVYZnwmFWJXX4DzI3zX9Kkw/r H9QVq3Ef6RpmVJCykrg0rSJGOGn0eis2b4+bU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48EF904E.6070004@xxxxxxxx>
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: <a55a39a90810100537l14197952k4dfef518f6527604@xxxxxxxxxxxxxx> <de76405a0810100545i35523668gc04705ea3c191b3c@xxxxxxxxxxxxxx> <a55a39a90810100600l3d9abe76u7b0bad194fc9f10b@xxxxxxxxxxxxxx> <48EF8579.4040201@xxxxxxxx> <a55a39a90810101012s74011087x6f66f2d17047db3@xxxxxxxxxxxxxx> <48EF904E.6070004@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanx a lot Jeremy!!

This is really going to be a lot of help.

Right now I am not very sure whether I will be able to use a 64-bit machine, but I will consider that options.
Thanx again for the help.   

On Fri, Oct 10, 2008 at 10:56 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
pallavi jk wrote:
Hi Jeremy,

Yes, I am planning to modify xen and the guest OS as well.

I need to trap every entry into the guest OS from user mode because I need to perform some checks in the hypervisor before transferring control to the guest OS.

If you run a 64-bit hypervisor, this will happen automatically.  Only 32-on-32 supports directly trapping from guest usermode to kernel.


So I need to avoid fast handlers which would directly transfer control to the guest OS, as I want to trap this entry first in the hypervisor. I need to do this as I intend to protect applications from a possibly malicious OS, so I want to perform some checks in the hypervisor.

I have just started studying the code. Can you please provide me guidelines about which source files and functions I should concentrate on?

arch/x86/**/traps.c is the first point to look at. Also entry.S which does the actual transfer of control between the various modes.  There are several variants of each file for different modes (32, 64, 32 compat on 64), so make sure you target the right ones.

  J

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>