From owner-freebsd-acpi@FreeBSD.ORG Thu May 26 20:33:37 2011 Return-Path: Delivered-To: acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16B51106566C for ; Thu, 26 May 2011 20:33:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 679AB8FC17 for ; Thu, 26 May 2011 20:33:35 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA25864; Thu, 26 May 2011 23:19:25 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QPh1h-0000iD-29; Thu, 26 May 2011 23:19:25 +0300 Message-ID: <4DDEB5CC.4050500@FreeBSD.org> Date: Thu, 26 May 2011 23:19:24 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Nate Lawson References: <4DDEA91F.8080008@root.org> In-Reply-To: <4DDEA91F.8080008@root.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@FreeBSD.org Subject: Re: paper on reverse-engineering drivers X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 20:33:37 -0000 on 26/05/2011 22:25 Nate Lawson said the following: > This might be a useful source for making ACPI compatible with Windows. > > http://dslab.epfl.ch/pubs/revnic > > I had thought of a project like this before. My idea was to take QEMU > and map PCI config space and allow direct access to the bare hardware > for only one device. The developer would install Windows in this QEMU > image on a system with the target device, identify it by its PCI id, and > then run Windows normally. The VM would log the driver's accesses to > config space as well as use CoW semantics for DMA accesses to memory and > IO ports. Something like this? http://www.serialice.com/News/News.html > Now that Intel/AMD support hardware virtualization and DMA isolation, it > would be better to do this with a modified Xen hypervisor. -- Andriy Gapon