From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M02Wg-0000fX-Gn
	for qemu-devel@nongnu.org; Fri, 01 May 2009 19:52:18 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M02Wb-0000eV-J0
	for qemu-devel@nongnu.org; Fri, 01 May 2009 19:52:17 -0400
Received: from [199.232.76.173] (port=55008 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M02Wb-0000eR-9E
	for qemu-devel@nongnu.org; Fri, 01 May 2009 19:52:13 -0400
Received: from mx20.gnu.org ([199.232.41.8]:42503)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1M02Wb-0005M2-1Z
	for qemu-devel@nongnu.org; Fri, 01 May 2009 19:52:13 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1M02WZ-0002qa-RH
	for qemu-devel@nongnu.org; Fri, 01 May 2009 19:52:12 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 7/8] Introduce reset notifier order
Date: Sat, 2 May 2009 00:52:06 +0100
References: <20090501211717.24514.23246.stgit@mchn012c.ww002.siemens.net>
	<20090501211721.24514.45545.stgit@mchn012c.ww002.siemens.net>
In-Reply-To: <20090501211721.24514.45545.stgit@mchn012c.ww002.siemens.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905020052.07059.paul@codesourcery.com>
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: Jan Kiszka <jan.kiszka@siemens.com>, Anthony Liguori <aliguori@us.ibm.com>, Avi Kivity <avi@redhat.com>

On Friday 01 May 2009, Jan Kiszka wrote:
> Add the parameter 'order' to qemu_register_reset and sort callbacks on
> registration. On system reset, callbacks with lower order will be
> invoked before those with higher order. Update all existing users to the
> standard order 0.
>
> Note: At least for x86, the existing users seem to assume that handlers
> are called in their registration order. Therefore, the patch preserves
> this property. If someone feels bored, (s)he could try to identify this
> dependency and express it properly on callback registration.

Why do we need this? Why isn't creation order good enough?

Paul