From: Anthony Liguori <aliguori@us.ibm.com>
To: Ewan Mellor <ewan@xensource.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
xen-devel@lists.xensource.com,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: xm list d flag?
Date: Sat, 01 Oct 2005 14:45:35 -0500 [thread overview]
Message-ID: <433EE75F.9090606@us.ibm.com> (raw)
In-Reply-To: <20051001144045.GA12651@uk.xensource.com>
Ewan Mellor wrote:
>A "dying" domain is one that completed shutdown (be it a halt, reboot, crash,
>or suspend) and that Xen is trying to destroy. If it cannot destroy it, then
>that means that someone is holding references to pages that belong to it. For
>example, if a driver backend fails to die, then the domain will stay around
>(probably indefinitely). Such an occurrence is a bug.
>
>
One thing to consider is having the drivers destroy the backend devices
on a @releaseDomain watch instead of on the front-end path disappearing.
@releaseDomain wasn't available when the drivers were first written so
it wasn't an option then.
This means that Xend does not have to be involved at all in device
tear-down (except for the higher level stuff when the domain goes away
completely).
This should more or less solve the zombie domain problem for good.
Thoughts?
Regards,
Anthony Liguori
>Ewan.
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>
>
next prev parent reply other threads:[~2005-10-01 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 12:17 xm list d flag? Ted Kaczmarek
2005-10-01 13:09 ` NAHieu
2005-10-01 14:40 ` Ewan Mellor
2005-10-01 19:45 ` Anthony Liguori [this message]
2005-10-01 20:46 ` Christian Limpach
2005-10-02 1:47 ` Anthony Liguori
2005-10-02 3:29 ` Christian Limpach
2005-10-03 22:58 ` Anthony Liguori
2005-10-04 0:14 ` Christian Limpach
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=433EE75F.9090606@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=ewan@xensource.com \
--cc=rusty@rustcorp.com.au \
--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.