From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Nc0h3-0006eq-Ef
	for qemu-devel@nongnu.org; Mon, 01 Feb 2010 13:08:13 -0500
Received: from [199.232.76.173] (port=57565 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Nc0h2-0006ei-1j
	for qemu-devel@nongnu.org; Mon, 01 Feb 2010 13:08:12 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <lcapitulino@redhat.com>) id 1Nc0gz-0006nT-5H
	for qemu-devel@nongnu.org; Mon, 01 Feb 2010 13:08:11 -0500
Received: from mx1.redhat.com ([209.132.183.28]:1025)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1Nc0gy-0006nL-Pq
	for qemu-devel@nongnu.org; Mon, 01 Feb 2010 13:08:09 -0500
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
	(int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o11I872Z009414
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Mon, 1 Feb 2010 13:08:07 -0500
From: Luiz Capitulino <lcapitulino@redhat.com>
Date: Mon,  1 Feb 2010 16:07:46 -0200
Message-Id: <1265047668-15039-1-git-send-email-lcapitulino@redhat.com>
Subject: [Qemu-devel] [RFC 0/2]: QMP DISK_ERROR event
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: kwolf@redhat.com

 Hi there,

 I've been requested by libvirt guys to add a QMP event for disk I/O errors,
this is what this series is about.

 It's a RFC because I need feedback on the following:

1. drive_get_on_error() is called on all disk errors, right?
2. I've tested only ENOSPC errors, is there a way to test other errors? Like
read ones?
3. Is this the right approach at all? :)

 Thanks.