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

Re: [Xen-devel] vcpu_info


  • To: "George Dunlap" <George.Dunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "pallavi jk" <pallutai@xxxxxxxxx>
  • Date: Fri, 10 Oct 2008 18:30:39 +0530
  • Cc:
  • Delivery-date: Fri, 10 Oct 2008 06:01:03 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=uLkCc+cIG/f2v+e2CQGuzqJnNzMJNieY6AcF0H0ChHzVZv9jVEzekvpQcVMQKubdQR z/ALXp5UdzfRjiob5Bk4bspJM1uPLLCcfTGMNjS0wbJz6IoLtuLNy/XspjPMcdJEQVW2 S9E40E9xU1P2jCqPWylKEQaAODpCtDgRC4j5U=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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??

On Fri, Oct 10, 2008 at 6:15 PM, George Dunlap <George.Dunlap@xxxxxxxxxxxxx> wrote:
It's worth a shot looking there.  Certainly 3+ will have it for sure.

Is there a particular reason you want to avoid that struct?

 -George

On Fri, Oct 10, 2008 at 1:37 PM, pallavi jk <pallutai@xxxxxxxxx> wrote:
> Can anyone please tell me what was the xen version in which struct vcpu_info
> was not present?
>
> Should I see in xen 2.0 ?...I need a xen version without "struct vcpu_info"
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

_______________________________________________
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®.