From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c9Ut6-0006Q3-Do for qemu-devel@nongnu.org; Wed, 23 Nov 2016 05:34:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c9Ut5-00007h-KY for qemu-devel@nongnu.org; Wed, 23 Nov 2016 05:34:48 -0500 Sender: Paolo Bonzini References: <1479357400-17441-1-git-send-email-alastair@au1.ibm.com> <1479357400-17441-3-git-send-email-alastair@au1.ibm.com> <3888651b-fd60-e827-a9f8-575a8f01be72@redhat.com> <1479853887.11116.95.camel@au1.ibm.com> <6d4e34f8-4b0b-85f2-93d6-6f0b3e2e7fb3@redhat.com> <1479856790.11116.111.camel@au1.ibm.com> <1761115996.1384447.1479894181425.JavaMail.zimbra@redhat.com> <20161123100558.GW9606@toto> From: Paolo Bonzini Message-ID: Date: Wed, 23 Nov 2016 11:34:38 +0100 MIME-Version: 1.0 In-Reply-To: <20161123100558.GW9606@toto> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH 2/4] qtest: Support named interrupts List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Edgar E. Iglesias" Cc: Peter Maydell , Alastair D'Silva , Andrew Jeffery , qemu-devel@nongnu.org, qemu-arm@nongnu.org, Joel Stanley , =?UTF-8?Q?C=c3=a9dric_Le_Goater?= On 23/11/2016 11:05, Edgar E. Iglesias wrote: >> > >> > But in general, the idea is that the qtest acts as the CPU. The test >> > cases can control the passing of time precisely, and they can _observe_ >> > additional events (such as interrupts or GPIO lines) but they don't inject >> > anything that the CPU cannot inject. The reason is to make the tests >> > more like small programs. It does mean that you are limited by the >> > connections of the board. > Hi Paolo, > > At some point we added support for using Qtest together with emulated > CPUs. In those cases, Qtest acts more like a test access port that can > access stuff within the VM. It can be used to test devices in combination > with guest SW. > > IMO, raising and lowering signals is useful and extending it to support > named interrupts seems like a useful feature to me... Fair enough! Paolo