From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37897) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqetj-0005cN-Dw for qemu-devel@nongnu.org; Fri, 08 May 2015 05:48:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yqetg-0005MS-2X for qemu-devel@nongnu.org; Fri, 08 May 2015 05:48:47 -0400 Received: from szxga01-in.huawei.com ([58.251.152.64]:24025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqetf-0005La-77 for qemu-devel@nongnu.org; Fri, 08 May 2015 05:48:43 -0400 Message-ID: <554C865B.8050807@huawei.com> Date: Fri, 8 May 2015 17:48:11 +0800 From: Shannon Zhao MIME-Version: 1.0 References: <1430990964-10528-1-git-send-email-zhaoshenglong@huawei.com> In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH v6 00/22] Generate ACPI v5.1 tables and expose them to guest over fw_cfg on ARM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: hangaohuai@huawei.com, "Michael S. Tsirkin" , Alexander Spyridakis , Claudio Fontana , QEMU Developers , "Huangpeng (Peter)" , =?UTF-8?B?QWxleCBCZW5uw6ll?= , Hanjun Guo , Igor Mammedov , Paolo Bonzini , Laszlo Ersek , Christoffer Dall , Shannon Zhao Hi Peter, On 2015/5/8 0:34, Peter Maydell wrote: > Hi. I've had a look through these patches now, and sent some mails > for a couple of specific issues. For the rest, this is what I'd > like to see for me to pull this in to target-arm: > Thanks for your review comments. > (1) acks or reviewed-by from one of the QEMU ACPI folk for any > patch that's touching generic ACPI code. Yeah, Igor said he will give reviewed-by for these patches. > (2) series should pass checkpatch.pl (you have a lot of overlong lines > warnings at the moment). Sorry, I will fix patch 07/22， but to patch 01/22， as I just move the file, maybe I don't need to deal the formats error of acpi-defs.h. Right? > (3) we shouldn't generate any ACPI tables or information where the > corresponding kernel code hasn't been accepted into mainline or > the arm64 tree; if there's anything here which isn't covered by > the accepted ACPI patches we should postpone that til the kernel > parts are in. > There are uart, virtio-mmio, PCIe whose kernel patches are not accepted into kernel mainline. For PCIe I think this is harmless. The PCIe ACPI table's format don't need to change even though the kernel code changes because it's defined by PCI firmware SPEC. For virtio-mmio the kernel code just add acpi_match_table for kernel driver to probe the device by ACPI. To be honestly the only thing will be changed is the _HID and this change is very small. It's same with uart. In a word, the only thing will be changed is the _HID of virtio-mmio and uart. But if we get these tables in, it's useful for people to test the corresponding kernel code. > If item (3) seems too awkward or harsh as a criterion I'm > open to discussion about it, but my feeling is that I'd > rather not start emitting tables until they're definitely > nailed down in format by being in the kernel. > > Finally, if you have some prebuilt images and command lines that > would be helpful, since I can put them into my local set of > things I run to check for breakage before making ARM pull requests. Ok. -- Shannon