From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KtNBY-0001RM-3R
	for qemu-devel@nongnu.org; Fri, 24 Oct 2008 09:58:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KtNBV-0001PR-8H
	for qemu-devel@nongnu.org; Fri, 24 Oct 2008 09:58:38 -0400
Received: from [199.232.76.173] (port=54877 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KtNBV-0001PL-37
	for qemu-devel@nongnu.org; Fri, 24 Oct 2008 09:58:37 -0400
Received: from mx2.redhat.com ([66.187.237.31]:48987)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <glommer@redhat.com>) id 1KtNBU-0003ZM-Ic
	for qemu-devel@nongnu.org; Fri, 24 Oct 2008 09:58:36 -0400
From: Glauber Costa <glommer@redhat.com>
Date: Fri, 24 Oct 2008 13:55:14 -0200
Message-Id: <1224863716-23793-1-git-send-email-glommer@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] Add generic infrastructure to trace I/O
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, avi@redhat.com

Hi guys,

Based on the discussions we had yesterday about the accel, me and anthony
had discussions that led us to think that the best way to avoid accel
hooks in the io operations is to generically keep track of I/O that 
happens throughout the execution. To demonstrate how this can be useful
besides the accelerator scope, I wrote an info iostats monitor command.

Comments welcome