From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=55843 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PAUTH-0003fo-M1 for qemu-devel@nongnu.org; Mon, 25 Oct 2010 17:20:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PAUTF-0001CO-8J for qemu-devel@nongnu.org; Mon, 25 Oct 2010 17:20:47 -0400 Received: from mail-qy0-f173.google.com ([209.85.216.173]:52203) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PAUTF-0001CA-44 for qemu-devel@nongnu.org; Mon, 25 Oct 2010 17:20:45 -0400 Received: by qyl33 with SMTP id 33so2049357qyl.4 for ; Mon, 25 Oct 2010 14:20:44 -0700 (PDT) Message-ID: <4CC5F4AE.6020306@codemonkey.ws> Date: Mon, 25 Oct 2010 16:20:46 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: backdoor References: <87vd4q5yqd.fsf_-_@ginnungagap.bsc.es> <4CC5783C.8060009@redhat.com> <87pquy4cn7.fsf@ginnungagap.bsc.es> In-Reply-To: <87pquy4cn7.fsf@ginnungagap.bsc.es> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , qemu-devel@nongnu.org On 10/25/2010 08:37 AM, Lluís wrote: > Paolo Bonzini writes: > > >> On 10/25/2010 12:54 PM, Lluís wrote: >> >>> * Backdoor channels need to provide arguments. >>> * It's better to provide the same mechanism for both *-user and softmmu >>> (otherwise the application to simulate or the interposed librariy >>> should be compiled differently on every case). >>> > >> You can add the syscall and, if it returns with ENOSYS, fall back to MMIO/PIO >> (you don't really need a special driver, only some chmod since BARs are >> accessible from /sys) or watchpoint/breakpoint. >> > That sounds nice, but would only work with Linux. I, for example, did > some full-system simulations with a QNX guest. > > I know extending the ISA is not nice at all, but I think that's much > more maintainable than a per-guest OS interface (supposing some will > need extra guest drivers). > On x86, there are some architecturally nicer ways to do this. For instance, a CPUID leaf could be used in the 0x40001xxx range. Regards, Anthony Liguori