All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Wang <wei.w.wang@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com,
	liliang.opensource@gmail.com, yang.zhang.wz@gmail.com,
	quan.xu0@gmail.com, nilal@redhat.com, riel@redhat.com
Subject: Re: [virtio-dev] Re: [PATCH v4 3/4] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT
Date: Wed, 14 Mar 2018 14:03:19 +0800	[thread overview]
Message-ID: <5AA8BB27.6030205@intel.com> (raw)
In-Reply-To: <20180314045130-mutt-send-email-mst@kernel.org>

On 03/14/2018 10:53 AM, Michael S. Tsirkin wrote:
> On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote:
>> On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
>>> On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
>>>
>>>> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
>>>> Signed-off-by: Liang Li <liang.z.li@intel.com>
>>>> CC: Michael S. Tsirkin <mst@redhat.com>
>>>> CC: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>>> CC: Juan Quintela <quintela@redhat.com>
>>> I find it suspicious that neither unrealize nor reset
>>> functions have been touched at all.
>>> Are you sure you have thought through scenarious like
>>> hot-unplug or disabling the device by guest?
>> OK. I think we can call balloon_free_page_stop in unrealize and reset.
>>
>>
>>> +static void *virtio_balloon_poll_free_page_hints(void *opaque)
>>> +{
>>> +    VirtQueueElement *elem;
>>> +    VirtIOBalloon *dev = opaque;
>>> +    VirtQueue *vq = dev->free_page_vq;
>>> +    uint32_t id;
>>> +    size_t size;
>>> What makes it safe to poke at this device from multiple threads?
>>> I think that it would be safer to do it from e.g. BH.
>>>
>> Actually the free_page_optimization thread is the only user of free_page_vq,
>> and there is only one optimization thread each time. Would this be safe
>> enough?
>>
>> Best,
>> Wei
> Aren't there other fields there? Also things like reset affect all VQs.
>

Yes. But I think BHs are used to avoid re-entrancy, which isn't the 
issue here.

The potential issue I could observe here is that 
"dev->free_page_report_status" is read and written by the optimization 
thread, and it is also modified by the migration thread and reset via 
virtio_balloon_free_page_stop.

How about adding a QEMU SpinLock, like this:

virtio_balloon_poll_free_page_hints()
{

     while (1) {
         qemu_spin_lock();
         /* If the status has been changed to STOP or EXIT, or the VM is 
stopped, just exit */
         if (dev->free_page_report_status >= FREE_PAGE_REPORT_S_STOP || 
!runstate_is_running()) {
             qemu_spin_unlock();
             break;
         }
         ....
         qemu_spin_unlock();
     }
}


Best,
Wei

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


WARNING: multiple messages have this Message-ID (diff)
From: Wei Wang <wei.w.wang@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com,
	liliang.opensource@gmail.com, yang.zhang.wz@gmail.com,
	quan.xu0@gmail.com, nilal@redhat.com, riel@redhat.com
Subject: Re: [Qemu-devel] [virtio-dev] Re: [PATCH v4 3/4] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT
Date: Wed, 14 Mar 2018 14:03:19 +0800	[thread overview]
Message-ID: <5AA8BB27.6030205@intel.com> (raw)
In-Reply-To: <20180314045130-mutt-send-email-mst@kernel.org>

On 03/14/2018 10:53 AM, Michael S. Tsirkin wrote:
> On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote:
>> On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
>>> On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
>>>
>>>> Signed-off-by: Wei Wang <wei.w.wang@intel.com>
>>>> Signed-off-by: Liang Li <liang.z.li@intel.com>
>>>> CC: Michael S. Tsirkin <mst@redhat.com>
>>>> CC: Dr. David Alan Gilbert <dgilbert@redhat.com>
>>>> CC: Juan Quintela <quintela@redhat.com>
>>> I find it suspicious that neither unrealize nor reset
>>> functions have been touched at all.
>>> Are you sure you have thought through scenarious like
>>> hot-unplug or disabling the device by guest?
>> OK. I think we can call balloon_free_page_stop in unrealize and reset.
>>
>>
>>> +static void *virtio_balloon_poll_free_page_hints(void *opaque)
>>> +{
>>> +    VirtQueueElement *elem;
>>> +    VirtIOBalloon *dev = opaque;
>>> +    VirtQueue *vq = dev->free_page_vq;
>>> +    uint32_t id;
>>> +    size_t size;
>>> What makes it safe to poke at this device from multiple threads?
>>> I think that it would be safer to do it from e.g. BH.
>>>
>> Actually the free_page_optimization thread is the only user of free_page_vq,
>> and there is only one optimization thread each time. Would this be safe
>> enough?
>>
>> Best,
>> Wei
> Aren't there other fields there? Also things like reset affect all VQs.
>

Yes. But I think BHs are used to avoid re-entrancy, which isn't the 
issue here.

The potential issue I could observe here is that 
"dev->free_page_report_status" is read and written by the optimization 
thread, and it is also modified by the migration thread and reset via 
virtio_balloon_free_page_stop.

How about adding a QEMU SpinLock, like this:

virtio_balloon_poll_free_page_hints()
{

     while (1) {
         qemu_spin_lock();
         /* If the status has been changed to STOP or EXIT, or the VM is 
stopped, just exit */
         if (dev->free_page_report_status >= FREE_PAGE_REPORT_S_STOP || 
!runstate_is_running()) {
             qemu_spin_unlock();
             break;
         }
         ....
         qemu_spin_unlock();
     }
}


Best,
Wei

  reply	other threads:[~2018-03-14  6:00 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07 12:34 [virtio-dev] [PATCH v4 0/4] virtio-balloon: free page hint reporting support Wei Wang
2018-03-07 12:34 ` [Qemu-devel] " Wei Wang
2018-03-07 12:34 ` [virtio-dev] [PATCH v4 1/4] bitmap: bitmap_count_one_with_offset Wei Wang
2018-03-07 12:34   ` [Qemu-devel] " Wei Wang
2018-03-14 16:20   ` Dr. David Alan Gilbert
2018-03-07 12:34 ` [virtio-dev] [PATCH v4 2/4] migration: API to clear bits of guest free pages from the dirty bitmap Wei Wang
2018-03-07 12:34   ` [Qemu-devel] " Wei Wang
2018-03-14 18:11   ` Dr. David Alan Gilbert
2018-03-14 19:16     ` [virtio-dev] " Michael S. Tsirkin
2018-03-14 19:16       ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14 19:42       ` Dr. David Alan Gilbert
2018-03-14 20:38         ` [virtio-dev] " Michael S. Tsirkin
2018-03-14 20:38           ` [Qemu-devel] " Michael S. Tsirkin
2018-03-15 11:10         ` [virtio-dev] " Wei Wang
2018-03-15 11:10           ` [Qemu-devel] " Wei Wang
2018-03-15 10:52     ` [virtio-dev] " Wei Wang
2018-03-15 10:52       ` [Qemu-devel] " Wei Wang
2018-03-15 13:50       ` [virtio-dev] " Michael S. Tsirkin
2018-03-15 13:50         ` [Qemu-devel] " Michael S. Tsirkin
2018-03-16 11:24         ` [virtio-dev] " Wei Wang
2018-03-16 11:24           ` [Qemu-devel] " Wei Wang
2018-03-07 12:34 ` [virtio-dev] [PATCH v4 3/4] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT Wei Wang
2018-03-07 12:34   ` [Qemu-devel] " Wei Wang
2018-03-13 16:49   ` [virtio-dev] " Michael S. Tsirkin
2018-03-13 16:49     ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14  2:43     ` [virtio-dev] " Wei Wang
2018-03-14  2:43       ` [Qemu-devel] " Wei Wang
2018-03-14  2:53       ` Michael S. Tsirkin
2018-03-14  2:53         ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14  6:03         ` Wei Wang [this message]
2018-03-14  6:03           ` Wei Wang
2018-03-14 14:12           ` Michael S. Tsirkin
2018-03-14 14:12             ` [Qemu-devel] " Michael S. Tsirkin
2018-03-15  1:15             ` Wei Wang
2018-03-15  1:15               ` [Qemu-devel] " Wei Wang
2018-03-15  2:47               ` Michael S. Tsirkin
2018-03-15  2:47                 ` [Qemu-devel] " Michael S. Tsirkin
2018-03-15 10:24                 ` Wei Wang
2018-03-15 10:24                   ` [Qemu-devel] " Wei Wang
2018-03-15 13:53                   ` Michael S. Tsirkin
2018-03-15 13:53                     ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14 18:44   ` [Qemu-devel] " Dr. David Alan Gilbert
2018-03-07 12:34 ` [virtio-dev] [PATCH v4 4/4] migration: use the free page hint feature from balloon Wei Wang
2018-03-07 12:34   ` [Qemu-devel] " Wei Wang
2018-03-13 16:35   ` [virtio-dev] " Michael S. Tsirkin
2018-03-13 16:35     ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14  2:41     ` [virtio-dev] " Wei Wang
2018-03-14  2:41       ` [Qemu-devel] " Wei Wang
2018-03-14  2:51       ` [virtio-dev] " Michael S. Tsirkin
2018-03-14  2:51         ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14  6:50         ` [virtio-dev] " Wei Wang
2018-03-14  6:50           ` [Qemu-devel] " Wei Wang
2018-03-14 14:45           ` [virtio-dev] " Michael S. Tsirkin
2018-03-14 14:45             ` [Qemu-devel] " Michael S. Tsirkin
2018-03-14 19:49   ` Dr. David Alan Gilbert
2018-03-16 11:20     ` Wei Wang

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=5AA8BB27.6030205@intel.com \
    --to=wei.w.wang@intel.com \
    --cc=dgilbert@redhat.com \
    --cc=liliang.opensource@gmail.com \
    --cc=mst@redhat.com \
    --cc=nilal@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quan.xu0@gmail.com \
    --cc=quintela@redhat.com \
    --cc=riel@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=yang.zhang.wz@gmail.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.