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

Re: [Xen-tools] [PATCH] Clean up dom_get() usage


  • To: Dan Smith <danms@xxxxxxxxxx>
  • From: Christian Limpach <christian.limpach@xxxxxxxxx>
  • Date: Fri, 16 Sep 2005 20:22:14 +0100
  • Cc: Xen Tools Developers <xen-tools@xxxxxxxxxxxxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Fri, 16 Sep 2005 19:19:49 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dczGtf/Ov8r6d/1k7NWbEW8KDHKtg+wdJJ3wzwKbsuM7DX5U482pcYCoO3fa0s5W8Hk/iVTRVUtNIDI//vr7Js0Qe2yLS+VTkUJ3CVr6ULTZdl3voVLeyiAYBNdZNezzVqPIh2CluXnhwj9QXRtjXds+iFj8mWRi4OzboHLKv4M=
  • List-id: Xen control tools developers <xen-tools.lists.xensource.com>

On 9/15/05, Dan Smith <danms@xxxxxxxxxx> wrote:

The 1st hunk adds a random empty line, please avoid hunks like that in
the future.

> This patch adds sanity checks everywhere dom_get() is used.

I don't think the 3rd hunk is needed.  It would make more sense to
have a patch which replaces the magic dom0 domid by a global variable
indicating the domid of the domain where xend is running.

> In the case of XendDomainInfo.update(), if we get None back from
> dom_get(), we destroy ourselves.  I believe that this should be the
> desired behavior, but arguments to the contrary are welcome.

It's possibly a sensible behaviour, but I'd like to move away from
code which does stuff as a side effect.  We don't want to end up with
countless places doing random actions just because they happen to
notice a state change first.

     christian

_______________________________________________
Xen-tools mailing list
Xen-tools@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-tools


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.