From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUSur-0003MP-Vd for qemu-devel@nongnu.org; Tue, 15 May 2012 21:20:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SUSuq-0000ZI-Cy for qemu-devel@nongnu.org; Tue, 15 May 2012 21:20:37 -0400 Received: from gate.crashing.org ([63.228.1.57]:47664) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUSuq-0000Z0-3r for qemu-devel@nongnu.org; Tue, 15 May 2012 21:20:36 -0400 Message-ID: <1337131216.6727.116.camel@pasglop> From: Benjamin Herrenschmidt Date: Wed, 16 May 2012 11:20:16 +1000 In-Reply-To: <4FB2FAD0.603@codemonkey.ws> References: <1336625347-10169-1-git-send-email-benh@kernel.crashing.org> <1336625347-10169-9-git-send-email-benh@kernel.crashing.org> <4FB1A80C.1010103@codemonkey.ws> <20120515014204.GE30229@truffala.fritz.box> <4FB1B95A.20209@codemonkey.ws> <1337049166.6727.32.camel@pasglop> <4FB1C480.1030408@codemonkey.ws> <1337050942.6727.40.camel@pasglop> <4FB26212.5050409@codemonkey.ws> <1337118943.6727.93.camel@pasglop> <4FB2D291.1050003@codemonkey.ws> <1337123324.6727.101.camel@pasglop> <4FB2EDB2.5050305@codemonkey.ws> <1337128915.6727.112.camel@pasglop> <4FB2FAD0.603@codemonkey.ws> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 08/13] iommu: Introduce IOMMU emulation infrastructure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Alex Williamson , Richard Henderson , "Michael S. Tsirkin" , qemu-devel@nongnu.org, Eduard - Gabriel Munteanu On Tue, 2012-05-15 at 19:54 -0500, Anthony Liguori wrote: > > You certainly could do that but it may get a little weird dealing with the > return path. You'd have to return something like -EWOULDBLOCK and make sure you > handle that in the dispatch code appropriately. Hrm, our implementation of kvm_arch_handle_exit() always return "1" after a hypercall, forcing kvm_cpu_exec() to return back to the thread loop, so we should be ok to just set env->halted and return no ? Cheers, Ben.