To support query migration thread infomation, save and delete
thread(live_migration and multifdsend) information at thread
creation and finish.
Signed-off-by: Jiang Jiacheng
---
migration/migration.c | 5 +
migration/multifd.c | 5 +
2 files changed, 10 insertions(+)
diff --git a/migr
Introduce interface query-migrationthreads. The interface is used
to query information about migration threads and returns with
migration thread's name and its id.
Introduce threadinfo.c to manage threads with migration.
Signed-off-by: Jiang Jiacheng
---
migration/meson.build | 1 +
migration/
We need get more migration thread information to support
migration pin, especially thread name and its pid. Add an
qmp interface to query migration threads information.
v2 of:
https://lists.nongnu.org/archive/html/qemu-devel/2023-01/msg04618.html
diff to v2:
* remove the event that report thread
On 2023/1/30 22:03, Juan Quintela wrote:
> Jiang Jiacheng wrote:
>> On 2023/1/30 12:27, Juan Quintela wrote:
>>> Jiang Jiacheng wrote:
Introduce interface query-migrationthreads. The interface is use
with the migration thread name reported by qemu and returns with
migration thre
On 2023/1/30 22:04, Juan Quintela wrote:
> Jiang Jiacheng wrote:
>> On 2023/1/30 12:28, Juan Quintela wrote:
>>> Jiang Jiacheng wrote:
To support query migration thread infomation, save and delete
thread information at thread creation and end.
Signed-off-by: Jiang Jiacheng
On 2023/1/30 12:28, Juan Quintela wrote:
> Jiang Jiacheng wrote:
>> To support query migration thread infomation, save and delete
>> thread information at thread creation and end.
>>
>> Signed-off-by: Jiang Jiacheng
>
> Don't disagree with this, but if we create this on the sending side, why
On 2023/1/30 12:27, Juan Quintela wrote:
> Jiang Jiacheng wrote:
>> Introduce interface query-migrationthreads. The interface is use
>> with the migration thread name reported by qemu and returns with
>> migration thread name and its pid.
>> Introduce threadinfo.c to manage threads with migrati
On 2023/1/30 12:19, Juan Quintela wrote:
> Jiang Jiacheng wrote:
>> Report migration thread name to libvirt in order to
>> support query migration thread infomation by its name.
>>
>> Signed-off-by: Jiang Jiacheng
>> ---
>> migration/migration.c | 3 +++
>> migration/multifd.c | 5 -
>
To support query migration thread infomation, save and delete
thread information at thread creation and end.
Signed-off-by: Jiang Jiacheng
---
migration/migration.c | 4
migration/multifd.c | 4
2 files changed, 8 insertions(+)
diff --git a/migration/migration.c b/migration/migratio
Report migration thread name to libvirt in order to
support query migration thread infomation by its name.
Signed-off-by: Jiang Jiacheng
---
migration/migration.c | 3 +++
migration/multifd.c | 5 -
qapi/migration.json | 12
3 files changed, 19 insertions(+), 1 deletion(-)
We need get more migration thread information to support
migration pin, especially thread name and its pid. Add an
qmp interface to query migration thread information by its
name and report thread name when migration thread is started.
Jiang Jiacheng (3):
migration: report migration thread name
Introduce interface query-migrationthreads. The interface is use
with the migration thread name reported by qemu and returns with
migration thread name and its pid.
Introduce threadinfo.c to manage threads with migration.
Signed-off-by: Jiang Jiacheng
---
migration/meson.build | 1 +
migration
On 2023/1/12 3:04, Daniel P. Berrangé wrote:
> On Wed, Jan 11, 2023 at 07:00:53PM +, Dr. David Alan Gilbert wrote:
>> * Jiang Jiacheng via (qemu-devel@nongnu.org) wrote:
>>> From: Zheng Chuan
>>>
>>> Report multiFd related thread pid to libvirt i
From: Zheng Chuan
Report migration thread pid to libvirt in order to pin
migration thread to different cpu.
---
migration/migration.c | 3 +++
qapi/migration.json | 12
2 files changed, 15 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index 52b5d39244.
By default, the migration thread shares CPU resources with the VM process.
With migration pin, support pin migration thread to expected CPU list
to avoid preempting CPU resources of VM process.
To support migration pin, we need report migration related thread pid
to libvirt.
libvirt patches:
ht
From: Zheng Chuan
Report multiFd related thread pid to libvirt in order to
pin multiFd thread to different cpu.
---
migration/multifd.c | 4
qapi/migration.json | 12
2 files changed, 16 insertions(+)
diff --git a/migration/multifd.c b/migration/multifd.c
index 000ca4d4ec..f3
By default, the migration thread shares CPU resources with the VM process.
With migration pin, support pin migration thread to expected CPU list
to avoid preempting CPU resources of VM process.
To support migration pin, we need report migration related thread pid
to libvirt.
libvirt patches:
ht
From: Zheng Chuan
Report migration thread pid to libvirt in order to pin
migration thread to different cpu.
---
migration/migration.c | 3 +++
qapi/migration.json | 12
2 files changed, 15 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index 52b5d39244.
From: Zheng Chuan
Report multiFd related thread pid to libvirt in order to
pin multiFd thread to different cpu.
---
migration/multifd.c | 4
qapi/migration.json | 12
2 files changed, 16 insertions(+)
diff --git a/migration/multifd.c b/migration/multifd.c
index 000ca4d4ec..f3
19 matches
Mail list logo
