From: Jim Fehlig <jfehlig@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Marek Marczykowski <marmarek@invisiblethingslab.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
AL13N <alien@rmail.be>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: OT: xen libvirt issue
Date: Tue, 09 Apr 2013 08:15:26 -0600 [thread overview]
Message-ID: <5164227E.9050204@suse.com> (raw)
In-Reply-To: <20836.3074.239782.83930@mariner.uk.xensource.com>
Ian Jackson wrote:
> AL13N writes ("Re: [Xen-devel] OT: xen libvirt issue"):
>
>> i was more worried about the comments in the patch, ie: that it
>> changes how tools using this (libvirt maybe) would need to be
>> recoded.
>>
>
> Yes, in order to fully fix these races there are a number of libvirt
> patches needed as well. I don't know exactly which libvirt trees
> these are in but the libvirt fixes are pure fixes which won't break
> anything that's not already broken.
>
libvirt >= 1.0.2 contains all of the related fixes.
Jim
next prev parent reply other threads:[~2013-04-09 14:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 19:49 OT: xen libvirt issue AL13N
2013-04-05 8:21 ` Dario Faggioli
2013-04-05 11:13 ` George Dunlap
2013-04-08 4:22 ` Marek Marczykowski
2013-04-08 6:26 ` AL13N
2013-04-08 15:36 ` Jim Fehlig
2013-04-08 17:22 ` Stefano Stabellini
2013-04-08 17:57 ` AL13N
2013-04-08 15:46 ` Jim Fehlig
2013-04-08 16:09 ` Ian Jackson
2013-04-08 17:53 ` AL13N
2013-04-09 12:39 ` Ian Jackson
2013-04-09 12:52 ` AL13N
2013-04-09 14:41 ` Jim Fehlig
2013-04-09 21:50 ` AL13N
2013-04-10 0:42 ` Jim Fehlig
2013-04-10 10:23 ` AL13N
2013-04-09 14:15 ` Jim Fehlig [this message]
2013-04-09 14:18 ` Ian Jackson
2013-04-09 21:48 ` AL13N
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=5164227E.9050204@suse.com \
--to=jfehlig@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=alien@rmail.be \
--cc=dario.faggioli@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--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 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.