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@lists.xensource.com http://lists.xensource.com/xen-devel
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..?? 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@lists.xensource.com > http://lists.xensource.com/xen-develPlease 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@lists.xensource.com http://lists.xensource.com/xen-devel
> 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?First, Dom0 initialises start_info in DomU''s memory. When it is finished with the domain build, it hands the control over to DomU, making sure that the location of the shared_info structure is know to DomU''s kernel. It does so, by saving pointer to start_info struct in register %esi (look in vcpu_x86_32 defined in tools/libxc/xc_dom_x86.c). When DomU kernel is executed, the first thing it does, is to save the %esi to xen_start_info symbol (look in startup_32 definied in arch/i386/kernel/head-xen.S). xen_start_info is then available for later use.> > 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??Python tools will take over (that''s what executed domain_builder in the first place) and unpause the domain after all the other bits and pieces are set up. Xen will schedule DomU according to its built-in policy.>Cheers Gr(z)egor(z) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> 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@lists.xensource.com >> 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@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel