From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jim Fehlig <jfehlig@novell.com>
Cc: LibVir <libvir-list@redhat.com>,
xen-devel <xen-devel@lists.xensource.com>,
Markus Gross <gross@univention.de>
Subject: Re: [libvirt] [PATCH] libxenlight driver
Date: Mon, 21 Feb 2011 17:15:03 +0000 [thread overview]
Message-ID: <20110221171503.GK3172@redhat.com> (raw)
In-Reply-To: <4D5DCB44.3060909@novell.com>
On Thu, Feb 17, 2011 at 06:28:36PM -0700, Jim Fehlig wrote:
> Here's the latest version of a libxenlight driver for libvirt.
>
> I've added a per-domain libxl_ctx in addition to the driver wide
> context. The former is stored in virDomainObject privateData and used
> for operations on the domain. The latter is stored in driver private
> data and is used for non-domain related libxl calls, e.g. getVersion,
> getNodeInfo, etc. This approach was suggested by Ian Jackson and
> Stefano Stabellini and appears to be working much better than a single,
> driver wide libxl_ctx. I no longer have the restart issues described in
> the first patch posting [1].
>
> Your review and comments are much appreciated!
I've not had a chance todo a proper review yet, but after skimming
the patch I think your impl / architecture looks pretty good.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2011-02-21 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 1:28 [PATCH] libxenlight driver Jim Fehlig
2011-02-18 11:15 ` Stefano Stabellini
2011-02-23 3:46 ` Jim Fehlig
2011-02-21 17:15 ` Daniel P. Berrange [this message]
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=20110221171503.GK3172@redhat.com \
--to=berrange@redhat.com \
--cc=gross@univention.de \
--cc=jfehlig@novell.com \
--cc=libvir-list@redhat.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.