There is no need to acquire the driver-wide lock in
libxlDomainDefineXML. When switching to jobs in the libxl
driver, most driver-wide locks were removed. The locking here
was preserved since I mistakenly thought virDomainObjListAdd
needed protection. This is not the case, so remove the
unnecess
On 18.09.2014 23:17, Jim Fehlig wrote:
There is no need to acquire the driver-wide lock in
libxlDomainDefineXML. When switching to jobs in the libxl
driver, most driver-wide locks were removed. The locking here
was preserved since I mistakenly thought virDomainObjListAdd
needed protection. Thi
Michal Privoznik wrote:
> On 18.09.2014 23:17, Jim Fehlig wrote:
>> There is no need to acquire the driver-wide lock in
>> libxlDomainDefineXML. When switching to jobs in the libxl
>> driver, most driver-wide locks were removed. The locking here
>> was preserved since I mistakenly thought virDoma