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 10/12] Move threadlet code to qemu-threadlets.c
Date: Tue, 18 Jan 2011 10:07:22 +0530 [thread overview]
Message-ID: <20110118043722.GA21383@linux.vnet.ibm.com> (raw)
In-Reply-To: <AANLkTin4os_2F8LHjyuAooERAPPniOmeDfbGVsy=WJnb@mail.gmail.com>
* Stefan Hajnoczi <stefanha@gmail.com> [2011-01-17 09:57:45]:
> On Thu, Jan 13, 2011 at 12:15 PM, Arun R Bharadwaj
> <arun@linux.vnet.ibm.com> wrote:
> > This patch moves the threadlet queue API code to
> > qemu-threadlets.c where these APIs can be used by
> > other subsystems.
>
> qemu-threadlet.c would be consistent with qemu-thread.c (not qemu-threads.c).
>
> Stefan
Sure. Makes sense.
next prev parent reply other threads:[~2011-01-18 4:37 UTC|newest]
Thread overview: 27+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-01-20 12:33 [Qemu-devel] [PATCH 00/12] Threadlet Infrastructure Arun R Bharadwaj
2011-01-20 12:34 ` [Qemu-devel] [PATCH 10/12] Move threadlet code to qemu-threadlets.c Arun R Bharadwaj
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=20110118043722.GA21383@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).