From: Juan Quintela <quintela@redhat.com>
To: Jiang Jiacheng <jiangjiacheng@huawei.com>
Cc: <qemu-devel@nongnu.org>, <berrange@redhat.com>,
<dgilbert@redhat.com>, <yubihong@huawei.com>,
<xiexiangyou@huawei.com>, <zhengchuan@huawei.com>,
<linyilu@huawei.com>
Subject: Re: [PATCH 2/3] migration: implement query migration threadinfo by name
Date: Tue, 31 Jan 2023 17:33:16 +0100 [thread overview]
Message-ID: <87edray88j.fsf@secure.mitica> (raw)
In-Reply-To: <07cad820-0755-2da9-e4d7-4e00f7b3a8f7@huawei.com> (Jiang Jiacheng's message of "Tue, 31 Jan 2023 21:00:03 +0800")
Jiang Jiacheng <jiangjiacheng@huawei.com> wrote:
> On 2023/1/30 22:03, Juan Quintela wrote:
>> Jiang Jiacheng <jiangjiacheng@huawei.com> 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.
>>>>
>>>
>>> It is only enough for migration pin which I want to implement. But I
>>> think this struct can be easily expand if we need other information
>>> about migration thread.
>>
>> I mean that pthread_t (what you are passing here) is an int on linux.
>> Not sure on other OS's.
>>
>
> I'm sorry about my misunderstanding. I use 'int' for thread-id just like
> cpu or iothread's thread-id, and it is get from 'qemu_get_thread_id'. So
> I think it is enough.
Ok, fine enough. Thanks.
Later, Juan.
next prev parent reply other threads:[~2023-01-31 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 8:47 [RFC PATCH 0/3] migration: support query migration thread information Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 1/3] migration: report migration thread name to libvirt Jiang Jiacheng via
2023-01-30 4:19 ` Juan Quintela
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-20 8:47 ` [PATCH 2/3] migration: implement query migration threadinfo by name Jiang Jiacheng via
2023-01-30 4:27 ` Juan Quintela
2023-01-30 12:48 ` Jiang Jiacheng via
2023-01-30 14:03 ` Juan Quintela
2023-01-31 13:00 ` Jiang Jiacheng via
2023-01-31 16:33 ` Juan Quintela [this message]
2023-01-20 8:47 ` [PATCH 3/3] migration: save/delete migration thread info Jiang Jiacheng via
2023-01-30 4:28 ` Juan Quintela
2023-01-30 12:49 ` Jiang Jiacheng via
2023-01-30 14:04 ` Juan Quintela
2023-01-31 13:00 ` Jiang Jiacheng via
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edray88j.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jiangjiacheng@huawei.com \
--cc=linyilu@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.com \
--cc=yubihong@huawei.com \
--cc=zhengchuan@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.