All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun R Bharadwaj <arun@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, aliguori@linux.vnet.ibm.com,
	jvrao@linux.vnet.ibm.com, qemu-devel@nongnu.org,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 00/12] Threadlets Infrastructure.
Date: Tue, 18 Jan 2011 10:08:45 +0530	[thread overview]
Message-ID: <20110118043845.GB21383@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTi=2UURM=e917QC=JHRZ_+rNs=3-szOSdPWRJDr_@mail.gmail.com>

* Stefan Hajnoczi <stefanha@gmail.com> [2011-01-17 10:32:24]:

> This series needs a new pair of eyes for review.  I'm probably missing
> things here after seeing it many times.
> 
> posix-aio-compat.c:handle_work() doesn't need to take aiocb_mutex for
> container_of(), which just calculates an address but doesn't actually
> access the aiocb.
> 
> dequeue_work_on_queue() is incorrect because a threadlet_worker() may
> remove the work item from the request_list just before we remove it
> again.  That double-remove is wrong and by not detecting this case we
> return success even though the work function may be running
> concurrently (and it's not safe to do anything with the work item at
> this time!).  Dequeue needs to lock the request_list, test if the item
> is still
> on the list, remove it if necessary, and return whether or not it was removed.
> 
> Stefan

I'll make the above changes with respect to handle_work() and
dequeue_work_on_queue().

Hopefully the patch series gets more review now that I have broken
down the patchset so that review becomes easier.

-arun

      reply	other threads:[~2011-01-18  4:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 12:14 [Qemu-devel] [PATCH 00/12] Threadlets Infrastructure Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 01/12] Add aiocb_mutex and aiocb_completion Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 02/12] Introduce work concept in posix-aio-compat.c Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 03/12] Add callback function to ThreadletWork structure Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 04/12] Add ThreadletQueue Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 05/12] Threadlet: Add submit_work threadlet API Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 06/12] Threadlet: Add dequeue_work threadlet API and remove active field Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 07/12] Remove thread_create routine Arun R Bharadwaj
2011-01-13 12:14 ` [Qemu-devel] [PATCH 08/12] Threadlet: Add aio_signal_handler threadlet API Arun R Bharadwaj
2011-01-17  9:56   ` Stefan Hajnoczi
2011-01-17 15:54     ` [Qemu-devel] " Paolo Bonzini
2011-01-17 17:38       ` Stefan Hajnoczi
2011-01-18  4:43     ` [Qemu-devel] " Arun R Bharadwaj
2011-01-18  6:31       ` Stefan Hajnoczi
2011-01-18  6:46         ` Arun R Bharadwaj
2011-01-18  7:14           ` Stefan Hajnoczi
2011-01-18 18:10             ` Venkateswararao Jujjuri (JV)
2011-01-19  7:54               ` Stefan Hajnoczi
2011-01-13 12:15 ` [Qemu-devel] [PATCH 09/12] Remove all instances of CONFIG_THREAD Arun R Bharadwaj
2011-01-13 12:15 ` [Qemu-devel] [PATCH 10/12] Move threadlet code to qemu-threadlets.c Arun R Bharadwaj
2011-01-17  9:57   ` Stefan Hajnoczi
2011-01-18  4:37     ` Arun R Bharadwaj
2011-01-13 12:15 ` [Qemu-devel] [PATCH 11/12] Threadlets: Add functionality to create private queues Arun R Bharadwaj
2011-01-13 12:15 ` [Qemu-devel] [PATCH 12/12] Threadlets: Add documentation Arun R Bharadwaj
2011-01-17 10:32 ` [Qemu-devel] [PATCH 00/12] Threadlets Infrastructure Stefan Hajnoczi
2011-01-18  4:38   ` Arun R Bharadwaj [this message]

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=20110118043845.GB21383@linux.vnet.ibm.com \
    --to=arun@linux.vnet.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.