Jiang Jiacheng wrote:
> On 2023/1/30 22:03, Juan Quintela wrote:
>> Jiang Jiacheng wrote:
>>> On 2023/1/30 12:27, Juan Quintela wrote:
1st, it is an int enough for all architectures? I know that for linux
and friends it is, but not sure about windows and other weird systems.
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
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 thread name and its pid.
>>> Introduce threadinfo.c to
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
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 migration.
>
> Signed-off-by: Jiang Jiacheng
I like
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 +
