[libvirt] [PATCH 2/6] Clarify the semantic of virDomainGetSchedulerParameters arguments

2011-05-18 Thread Matthias Bolte
params and nparams are essential and cannot be NULL. Check this in libvirt.c and remove redundant checks from the drivers (e.g. xend). Instead of enforcing that nparams must point to exact same value as returned by virDomainGetSchedulerType relax this to a lower bound check. This is what some

Re: [libvirt] [PATCH 2/6] Clarify the semantic of virDomainGetSchedulerParameters arguments

2011-05-18 Thread Daniel Veillard
On Wed, May 18, 2011 at 12:21:09PM +0200, Matthias Bolte wrote: params and nparams are essential and cannot be NULL. Check this in libvirt.c and remove redundant checks from the drivers (e.g. xend). Instead of enforcing that nparams must point to exact same value as returned by

Re: [libvirt] [PATCH 2/6] Clarify the semantic of virDomainGetSchedulerParameters arguments

2011-05-18 Thread Matthias Bolte
2011/5/18 Daniel Veillard veill...@redhat.com: On Wed, May 18, 2011 at 12:21:09PM +0200, Matthias Bolte wrote: params and nparams are essential and cannot be NULL. Check this in libvirt.c and remove redundant checks from the drivers (e.g. xend). Instead of enforcing that nparams must point to