All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Stefan Berger <stefanb@us.ibm.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] [Xen] [ACM] Code restructuring
Date: Tue, 24 Apr 2007 16:55:51 +0100	[thread overview]
Message-ID: <C253E717.DC73%keir@xensource.com> (raw)
In-Reply-To: <1177431435.4153.8.camel@gsal-3.watson.ibm.com>

Much nicer, thank you. I've applied it for 3.0.5. However, given the effort
put in to labelling a domain at the very start of its lifetime, wouldn't it
be a good idea to leave that label attached until the domain is actually
destroyed? This would correspond to putting the destructor call in
domain_destroy() or, even better, complete_domain_destroy(). Bear in mind
that a domain may still be accessible and have resources allocated to it
even after domain_kill() finishes executing. So stripping its resource label
at that point in time is a bit worrying.

 -- Keir

On 24/4/07 17:17, "Stefan Berger" <stefanb@us.ibm.com> wrote:

> This patch restructures part of the ACM code in Xen. When a domain is
> created, the function acm_domain_create() in domain_create() is called
> that does what previously the pre- and post_domain_create functions were
> doing. Similarly there's a function acm_domain_destroy() in
> domain_kill() that reverts changes to state when destroying a domain.
> There's no more separate initialization necessary for domain-0, but
> domain_create takes one more parameter, the ssidref. It is usually
> passed through the hypercall when a domain is created.
> 
> Signed-off-by: Stefan Berger <stefanb@us.ibm.com>

  reply	other threads:[~2007-04-24 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24 16:17 [PATCH] [Xen] [ACM] Code restructuring Stefan Berger
2007-04-24 15:55 ` Keir Fraser [this message]
2007-04-24 16:15   ` Stefan Berger
2007-04-24 20:33     ` Keir Fraser

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=C253E717.DC73%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=stefanb@us.ibm.com \
    --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.