From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Subject: Re: [PATCH 3/4] KVM: renumber architecture-dependent requests
Date: Fri, 8 Jan 2016 15:01:34 +0900
Message-ID: <568F50BE.209@lab.ntt.co.jp>
References: <1452176228-8484-1-git-send-email-pbonzini@redhat.com>
 <1452176228-8484-4-git-send-email-pbonzini@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Paul Mackerras <paulus@samba.org>
To: Paolo Bonzini <pbonzini@redhat.com>, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <1452176228-8484-4-git-send-email-pbonzini@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 2016/01/07 23:17, Paolo Bonzini wrote:
> Leave room for 4 more arch-independent requests.

In the current requests handling code, this ordering means
that architecture specific requests get handled only after
generic ones.

If someone wants to make a generic request that needs to be
handled before entering the guest from any architecture
specific request handler, this can be a problem.

If you can guarantee that this kind of dependencies will not
be introduced in the future, this change looks good to me.

Actually, I want to make the current dependencies, even between
architecture specific requests, more explicitly written in the
code.

  Takuya