)]}'
{"releasenotes/notes/bp-virt-driver-cpu-thread-pinning-1aaeeb6648f8e009.yaml":[{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"fc439d8e1f69a433352927c97308687dd01d8576","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  - Added support for CPU thread policies, which can be used"},{"line_number":7,"context_line":"    to control how the scheduler/virt driver places guests"},{"line_number":8,"context_line":"    with respect to CPU SMT \"threads\". These are provided"},{"line_number":9,"context_line":"    as instance and image metadata options and provide an"},{"line_number":10,"context_line":"    additional level of control over CPU pinning policy, when"},{"line_number":11,"context_line":"    compared to the existing CPU policy feature."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"fa69d971_567a3c25","line":9,"updated":"2016-01-11 21:39:01.000000000","message":"It seems useful to mention the options here.","commit_id":"a017e2b94a49ececb13aaae785c1ab5627b4a3b4"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"0e81922f7d7dff3c8de712b4b331b7e875a06fcf","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"prelude: \u003e"},{"line_number":3,"context_line":"    CPU pinning policy can now be further specified via CPU thread policies."},{"line_number":4,"context_line":"features:"},{"line_number":5,"context_line":"  - Added support for CPU thread policies, which can be used to control how"},{"line_number":6,"context_line":"    the scheduler/virt driver places guests with respect to CPU SMT \"threads\"."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"da6ed579_153e4ab8","line":3,"updated":"2016-01-13 17:47:25.000000000","message":"preludes are not used in normal reno adds, please remove this.","commit_id":"166f6395a7180a1e46bfb83c6d571370f7cc1bca"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"0e81922f7d7dff3c8de712b4b331b7e875a06fcf","unresolved":false,"context_lines":[{"line_number":7,"context_line":"    These are provided as instance and image metadata options,"},{"line_number":8,"context_line":"    \u0027hw:cpu_thread_policy\u0027 and \u0027hw_cpu_thread_policy\u0027 respectively, and"},{"line_number":9,"context_line":"    provide an additional level of control over CPU pinning policy, when"},{"line_number":10,"context_line":"    compared to the existing CPU policy feature."}],"source_content_type":"text/x-yaml","patch_set":2,"id":"da6ed579_f5b05645","line":10,"updated":"2016-01-13 17:47:25.000000000","message":"given that this didn\u0027t land with the changes that it represents, it is probably worth reference to the commits that did change this.","commit_id":"166f6395a7180a1e46bfb83c6d571370f7cc1bca"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"93a5763865f5ace7329bd34a471cfddc5eb12e73","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - Added support for CPU thread policies, which can be used to control how"},{"line_number":4,"context_line":"    the scheduler/virt driver places guests with respect to CPU SMT \"threads\"."},{"line_number":5,"context_line":"    These are provided as instance and image metadata options,"},{"line_number":6,"context_line":"    \u0027hw:cpu_thread_policy\u0027 and \u0027hw_cpu_thread_policy\u0027 respectively, and"},{"line_number":7,"context_line":"    provide an additional level of control over CPU pinning policy, when"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"9a68dd71_796af3b4","line":4,"range":{"start_line":4,"start_character":18,"end_line":4,"end_character":22},"updated":"2016-01-22 22:46:08.000000000","message":"is this libvirt only change?","commit_id":"ce01ffc90313e09a646d363ea3a95f8f37a853d2"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"21ae29f8f38fd73a3df83640d09601eb82e0ca19","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - Added support for CPU thread policies, which can be used to control how"},{"line_number":4,"context_line":"    the scheduler/virt driver places guests with respect to CPU SMT \"threads\"."},{"line_number":5,"context_line":"    These are provided as instance and image metadata options,"},{"line_number":6,"context_line":"    \u0027hw:cpu_thread_policy\u0027 and \u0027hw_cpu_thread_policy\u0027 respectively, and"},{"line_number":7,"context_line":"    provide an additional level of control over CPU pinning policy, when"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"9a68dd71_6e2b9595","line":4,"range":{"start_line":4,"start_character":18,"end_line":4,"end_character":22},"in_reply_to":"9a68dd71_796af3b4","updated":"2016-01-26 14:28:25.000000000","message":"It is, yes. Updated.","commit_id":"ce01ffc90313e09a646d363ea3a95f8f37a853d2"}]}