From: Jeremy Fitzhardinge <jeremy@goop.org>
To: pallavi jk <pallutai@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
xen-devel@lists.xensource.com
Subject: Re: vcpu_info
Date: Fri, 10 Oct 2008 10:26:38 -0700 [thread overview]
Message-ID: <48EF904E.6070004@goop.org> (raw)
In-Reply-To: <a55a39a90810101012s74011087x6f66f2d17047db3@mail.gmail.com>
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
next prev parent reply other threads:[~2008-10-10 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 12:37 vcpu_info pallavi jk
2008-10-10 12:45 ` vcpu_info George Dunlap
2008-10-10 13:00 ` vcpu_info pallavi jk
2008-10-10 16:40 ` vcpu_info Jeremy Fitzhardinge
2008-10-10 17:12 ` vcpu_info pallavi jk
2008-10-10 17:26 ` Jeremy Fitzhardinge [this message]
2008-10-10 17:59 ` vcpu_info pallavi jk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48EF904E.6070004@goop.org \
--to=jeremy@goop.org \
--cc=George.Dunlap@eu.citrix.com \
--cc=pallutai@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.