Re: [Xen-devel] [PATCH] add count-only option to DOM0_GETDOMAINI

There's a race condition here. There's no way of knowing that domainshaven't been destroyed (or created) in between these calls.
Unfortunately, the only way to avoid this is grab them one at a time.

The race condition is harmless and the patch is an improvement over thecurrent situation where you have to guess the number of domains (andhence the size of the buffer you allocate).

Most of the time the caller will be looking for a snapshot of domaininformation, not an up-to-the-instant comprehensive report.

And the pre-existing method of allocating a huge buffer and calling oncestill works.


Mike

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

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] add count-only option to DOM0_GETDOMAININFOLIST hypercall, Mike D. Day Re: [Xen-devel] [PATCH] add count-only option to DOM0_GETDOMAININFOLIST hypercall, Anthony Liguori Re: [Xen-devel] [PATCH] add count-only option to DOM0_GETDOMAININFOLIST hypercall, Mike D. Day <=

Previous by Date:

[Xen-devel] Re: [PATCH] fix compilation in traps.c with crash_debug=y [was Re: [Xen-changelog] Paravirtualise the CPUID instruction by forcing emulation with an invalid-opcode prefix.], Muli Ben-Yehuda

Next by Date:

Re: [Xen-devel] [PATCH] PCI Backend - Late Binding, Keir Fraser

Previous by Thread:

Re: [Xen-devel] [PATCH] add count-only option to DOM0_GETDOMAININFOLIST hypercall, Anthony Liguori

Next by Thread:

[Xen-devel] [PATCH] get register context from other vcpu's vmcs for gdbserver-xen user, Kamble, Nitin A

Indexes:

[Date] [Thread] [Top] [All Lists]