)]}'
{"doc/source/admin/cpu-topologies.rst":[{"author":{"_account_id":7730,"name":"Sahid Orentino Ferdjaoui","email":"sahid.ferdjaoui@industrialdiscipline.com","username":"sahid"},"change_message_id":"7c6314ae752fd9b8a958a05408e54c34c55fe004","unresolved":false,"context_lines":[{"line_number":274,"context_line":".. important::"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"   The functionality described below is currently only supported by the"},{"line_number":277,"context_line":"   libvirt/KVM and libvirt/QEMU driver."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"In addition to configuring how an instance is scheduled on host CPUs, it is"},{"line_number":280,"context_line":"possible to configure how CPUs are represented in the instance itself. By"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bf8cb3f7_b4ef38e8","line":277,"updated":"2017-12-20 15:43:37.000000000","message":"Not sure we want to add this. It\u0027s not something we want recommend even if using QEMU TGC is able to provide a CPU topology the behavior will be not as expected since in TGC all vCPUs are running in one thread.","commit_id":"a6027468058c67f3af24c3101a9db8ef3dbf32c6"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"ecf0579b23dbb02d5d3957d4c365a595db50341d","unresolved":false,"context_lines":[{"line_number":274,"context_line":".. important::"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"   The functionality described below is currently only supported by the"},{"line_number":277,"context_line":"   libvirt/KVM and libvirt/QEMU driver."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"In addition to configuring how an instance is scheduled on host CPUs, it is"},{"line_number":280,"context_line":"possible to configure how CPUs are represented in the instance itself. By"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bf8cb3f7_78e9977e","line":277,"in_reply_to":"bf8cb3f7_4c6c1c08","updated":"2017-12-21 03:03:14.000000000","message":"I have updated it with information as far as I found.","commit_id":"a6027468058c67f3af24c3101a9db8ef3dbf32c6"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"1e30d5562e79271ca6a2e1c53a3e5373677905ce","unresolved":false,"context_lines":[{"line_number":274,"context_line":".. important::"},{"line_number":275,"context_line":""},{"line_number":276,"context_line":"   The functionality described below is currently only supported by the"},{"line_number":277,"context_line":"   libvirt/KVM and libvirt/QEMU driver."},{"line_number":278,"context_line":""},{"line_number":279,"context_line":"In addition to configuring how an instance is scheduled on host CPUs, it is"},{"line_number":280,"context_line":"possible to configure how CPUs are represented in the instance itself. By"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bf8cb3f7_4c6c1c08","line":277,"in_reply_to":"bf8cb3f7_b4ef38e8","updated":"2017-12-21 00:17:25.000000000","message":"Good information, thanks! Then we should document that \"it currently works with libvirt/QEMU driver, but we don\u0027t recommend it because (cons)\" as a note or something.\n\nSo, it seems like I should look into this more deeply. Sahid, are there any documents for the behavior which we can refer in libvirt or qemu community??","commit_id":"a6027468058c67f3af24c3101a9db8ef3dbf32c6"}]}