Re: [PATCH v3 for Xen 4.6 1/4] xen: enable per-VCPU parameter settings for RTDS scheduler

[Dario Faggioli <dario.faggioli@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1639 bytes --]

So, about the structure of the patch/changelog/etc, taking this patch as
an example.

On Sun, 2015-06-28 at 21:44 -0500, Chong Li wrote:
> Add two hypercalls(XEN_DOMCTL_SCHEDOP_getvcpuinfo/putvcpuinfo) to get/set a domain's
> per-VCPU parameters.
> 
This is almost ok. Line should be shorter (try a `git log' with this
patch committed, and check how it looks).

Also, I'd rephrase it as "Add XEN_DOMCTL_SCHEDOP_getvcpuinfo and
_putvcpuinfo hypercalls to independently get and set the scheduling
parameters of each vCPU of a domain"

Or something like this.

> Changes on PATCH v2:
> 
So, this kind of summary goes below the '---', as we don't want it in
the final history. And what it should contain what actually changed
between previous versions and this one, while this...

> 1) Change struct xen_domctl_scheduler_op, for transferring per-vcpu parameters
> between libxc and hypervisor.
> 
> 2) Handler of XEN_DOMCTL_SCHEDOP_getinfo now just returns the default budget and period values of RTDS scheduler.
> 
> 3) Handler of XEN_DOMCTL_SCHEDOP_getvcpuinfo now can return a random subset of the parameters of the VCPUs of a specific domain
> 
... looks more like something that could actually be in the actual
changelog (so not under any 'Changes on PATCH v2' preamble), as it
dscribes how the hypercall interface looks like.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel