All of lore.kernel.org
 help / color / mirror / Atom feed
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 09:40:25 -0700	[thread overview]
Message-ID: <48EF8579.4040201@goop.org> (raw)
In-Reply-To: <a55a39a90810100600l3d9abe76u7b0bad194fc9f10b@mail.gmail.com>

pallavi jk wrote:
> Thanx George.
>
> Yes, am looking into xen-2.0. "struct vcpu_info" is not present there.
>
> Actually am doing a project in which i need to provide a functionality 
> similar to pushing the address of cr2 onto the stack.
>
> Also, how can I avoid the use of fast handlers?...I need to perform 
> some checks inside xen before transferring control to the guest OS for 
> each trap.
>
> Should I modify the "set_trap_table" hypercall for that??

It might help if you give a more complete description of what you're 
trying to achieve.  The list of things you're trying to do or want don't 
make a lot of sense on their own.

For example, are you modifying Xen?  Or just guest code?  If you're 
modifying Xen, it's pretty easy to remove the special case for trap 0x80.

    J

  reply	other threads:[~2008-10-10 16:40 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     ` Jeremy Fitzhardinge [this message]
2008-10-10 17:12       ` vcpu_info pallavi jk
2008-10-10 17:26         ` vcpu_info Jeremy Fitzhardinge
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=48EF8579.4040201@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.