xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 小黄豆 <vivagin@yeah.net>
To: Xen org <xen-devel@lists.xen.org>
Subject: Relationship between GuestOS shutdown and destroy operations?
Date: Fri, 21 Sep 2012 14:02:28 +0800 (CST)	[thread overview]
Message-ID: <507ae72.1b8c.139e76b8b4c.Coremail.vivagin@yeah.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]

Hello everyone!

In my opinion, I think when we shutdown the GuestOS,
 Xen should free allocated vcpu and domain gived to GuestOS 
when it created at the same time. 

But I don’t find any code in functions associated with shutdown process to
show this work,
for example: 
Hvm_vcpu_down()-〉domain_shutdown()->__domain_finalise_shutdown()

But I find the functions free_vcpu_struct() and free_domain_struct() 
in the function complete_domain_destroy() in the process of destroy
operation, 
the code process is:
Domain_kill()->put_domain()->domain_destroy()->complete_domain_destroy()

Is that process right? Is there any relationship between them?
Does anyone know it?

Thanks for your help!



--
View this message in context: http://xen.1045712.n5.nabble.com/Relationship-between-GuestOS-shutdown-and-destroy-operations-tp5711423.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

[-- Attachment #1.2: Type: text/html, Size: 1690 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2012-09-21  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21  6:02 小黄豆 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-21  4:35 Relationship between GuestOS shutdown and destroy operations? Bruce Granger
2012-09-21  8:07 ` Ian Campbell

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=507ae72.1b8c.139e76b8b4c.Coremail.vivagin@yeah.net \
    --to=vivagin@yeah.net \
    --cc=xen-devel@lists.xen.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).