From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60585) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfZXQ-0001ZN-Vl for qemu-devel@nongnu.org; Tue, 07 Apr 2015 15:51:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YfZXN-0002CT-79 for qemu-devel@nongnu.org; Tue, 07 Apr 2015 15:51:56 -0400 Received: from mail-ob0-x230.google.com ([2607:f8b0:4003:c01::230]:33467) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfZXN-0002C9-1M for qemu-devel@nongnu.org; Tue, 07 Apr 2015 15:51:53 -0400 Received: by oblw8 with SMTP id w8so56379125obl.0 for ; Tue, 07 Apr 2015 12:51:52 -0700 (PDT) Received: from t430.minyard.home (pool-173-57-158-30.dllstx.fios.verizon.net. [173.57.158.30]) by mx.google.com with ESMTPSA id jt2sm6982241oeb.13.2015.04.07.12.51.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Apr 2015 12:51:51 -0700 (PDT) Sender: Corey Minyard Received: from t430.minyard.home (t430.minyard.home [127.0.0.1]) by t430.minyard.home (8.14.7/8.14.7) with ESMTP id t37JpmoP024642 for ; Tue, 7 Apr 2015 14:51:49 -0500 Received: (from cminyard@localhost) by t430.minyard.home (8.14.7/8.14.7/Submit) id t37Jpmel024640 for qemu-devel@nongnu.org; Tue, 7 Apr 2015 14:51:48 -0500 From: minyard@acm.org Date: Tue, 7 Apr 2015 14:51:29 -0500 Message-Id: <1428436304-24044-1-git-send-email-minyard@acm.org> Subject: [Qemu-devel] [PATCH 00/15] IPMI device for qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This set of patches adds an IPMI KCS or BT interface to qemu, along with a local simulated baseboard management controller (BMC) and a way to connect to an external BMC. It is mostly unchanged from previous release, except for bug fixes and the following changes: The ACPI generation code custom to this was removed and it's now using the new aml-build code. Because of the previous change, capability was added to hook into the SSDT build process so that devices could insert their own table entries. Also because of this, and because Benjamin Herrenschmidt pointed out the need to have this on systems without SMBIOS and ACPI, that code has now been made optional. The SMBIOS uses TARGET_I386 to do this, which seems to be safe. The ACPI code required transfering the CONFIG_ACPI entry from the default configs to the target configs, in a new patch (patch 13). I'm not sure this was the best way, but adding a new file to do it got messy, and this seemed simple. Maybe there's a better way. Also, there's lots of config options for this, and I'm not sure they are really all necessary. Should there be just one CONFIG_IPMI that covers everything? Thanks, -corey