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

Re: [Xen-devel] how is start_info used by domU


  • To: Sandesh <sandesh.ahiremath@xxxxxxxxx>
  • From: "Grzegorz Miłoś" <gm281@xxxxxxxxx>
  • Date: Tue, 24 Jun 2008 19:35:34 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 24 Jun 2008 11:35:56 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=kK6zkHOWkNSoXOjjWdND2WOxbTev57bHcnfGQF6ZBG+BdGjQkBtNN2fGJGa+Qy1vcG gQfmKt0BwU1pXFLqSZLGT8tejMSXmFA2us+2ghcg5vuHm0EkE+R2OZHSjlovcu9lUlFE 06QxsRCbs1STTSx2PzxNHRmXoYlaUFdqM74fA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> also in xc_dom_boot_image
> dom->shared_info_mfn = domctl.u.getdomaininfo.shared_info_frame, but how
> does the shared_info_frame get the value in the first place..??

XEN_DOMCTL_getdomaininfo hypercall.
It's handled by getdomaininfo() definied in xen/common/domctl.c

Cheers
Gr(z)egor(z)

>
> Thanks,
>   Sandesh
> On Tue, 2008-06-24 at 17:44 +0530, Sandesh wrote:
>> Hi,
>>  I have a doubt regarding the way start_info fields are used by domU.
>> I see that in start_info_x86_32(), most fields of start_info are getting
>> initialized. I know that these info are used during the boot of guest
>> OS, but iam not able to figure out as to how exactly this is achieved in
>> the implementation?
>>
>> Another doubt i have is that the domain_builder executes vm_launch as
>> its last step which makes setvcpucontext hypercall. After this when will
>> it get loaded by the scheduler??
>>
>>  Correct me if my understanding is wrong.
>>
>> Thanks,
>>   Sandesh
>>
>>
>> Please do not print this email unless it is absolutely necessary.
>>
>> The information contained in this electronic message and any attachments to 
>> this message are intended for the exclusive use of the addressee(s) and may 
>> contain proprietary, confidential or privileged information. If you are not 
>> the intended recipient, you should not disseminate, distribute or copy this 
>> e-mail. Please notify the sender immediately and destroy all copies of this 
>> message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient should 
>> check this email and any attachments for the presence of viruses. The 
>> company accepts no liability for any damage caused by any virus transmitted 
>> by this email.
>>
>> www.wipro.com
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive use of the addressee(s) and may 
> contain proprietary, confidential or privileged information. If you are not 
> the intended recipient, you should not disseminate, distribute or copy this 
> e-mail. Please notify the sender immediately and destroy all copies of this 
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should 
> check this email and any attachments for the presence of viruses. The company 
> accepts no liability for any damage caused by any virus transmitted by this 
> email.
>
> www.wipro.com
>
> _______________________________________________
> 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®.