From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D239EC433DB for ; Wed, 3 Mar 2021 16:11:18 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 6E24864EE9 for ; Wed, 3 Mar 2021 16:11:18 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 6E24864EE9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:48764 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lHU5l-0007dN-H9 for qemu-devel@archiver.kernel.org; Wed, 03 Mar 2021 11:11:17 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:33572) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lHU46-0006FF-7c for qemu-devel@nongnu.org; Wed, 03 Mar 2021 11:09:34 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:45315) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from ) id 1lHU43-00047D-HL for qemu-devel@nongnu.org; Wed, 03 Mar 2021 11:09:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1614787770; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hqmQpQC1hIsiFSb48vVwvWR4Eo6rlW6WaGGt6sERSiI=; b=XC0uOfHHowHDEGh2R8mcYH2SOTX7akglCwT6Gd8NZ64PPf7RsVuqNVlNfN4TuwzyCJKVNv 2emU6EswOcH9C609JmXlrIKJPZ4FEA2ow3l2pEckGRVbic+0v4BlpSCrdD2rLc/YMNTKD6 3P5ts8W7seKxBlGUTl5JRMG+SYsaBS4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-202-nDxAXgI4PxeXDRe0d9RBJA-1; Wed, 03 Mar 2021 11:09:29 -0500 X-MC-Unique: nDxAXgI4PxeXDRe0d9RBJA-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E17FA107ACF9; Wed, 3 Mar 2021 16:09:27 +0000 (UTC) Received: from MiWiFi-RA69-srv (unknown [10.40.208.37]) by smtp.corp.redhat.com (Postfix) with ESMTP id B50621002393; Wed, 3 Mar 2021 16:09:18 +0000 (UTC) Date: Wed, 3 Mar 2021 17:09:16 +0100 From: Igor Mammedov To: Laszlo Ersek Subject: Re: [PATCH v1] acpi: increase maximum size for "etc/table-loader" blob Message-ID: <20210303170916.278cdcc2@MiWiFi-RA69-srv> In-Reply-To: <4bc8c306-48d2-8122-c096-dcac15170791@redhat.com> References: <20210301104833.45580-1-david@redhat.com> <20210302172323.6cac394a@MiWiFi-RA69-srv> <09fbdaa9-2882-2056-a5a2-2ca0da8c12cf@redhat.com> <7d8281a8-0479-ac81-c602-ed87c71ce3e2@redhat.com> <4bc8c306-48d2-8122-c096-dcac15170791@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=imammedo@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Received-SPF: pass client-ip=63.128.21.124; envelope-from=imammedo@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Peter Maydell , "Michael S. Tsirkin" , David Hildenbrand , Richard Henderson , qemu-devel@nongnu.org, Alistair Francis , Shannon Zhao , qemu-arm@nongnu.org, Paolo Bonzini Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, 3 Mar 2021 16:03:36 +0100 Laszlo Ersek wrote: > On 03/02/21 19:43, David Hildenbrand wrote: > > > We are dealing with different blobs here (tables_blob vs. cmd_blob). > > OK, thanks -- this was the important bit I was missing. Over time I've > lost track of the actual set of fw_cfg blobs that QEMU exposes, for the > purposes of the ACPI linker/loader. > > I've looked up the acpi_add_rom_blob() calls in "hw/i386/acpi-build.c" > and "hw/arm/virt-acpi-build.c": > > hw name max_size notes > ------- ------------------------------------------- ------------------------------------ ------ > > virt ACPI_BUILD_TABLE_FILE ("etc/acpi/tables") ACPI_BUILD_TABLE_MAX_SIZE (0x200000) n/a > virt ACPI_BUILD_LOADER_FILE ("etc/table-loader") 0 n/a > virt ACPI_BUILD_RSDP_FILE ("etc/acpi/rsdp") 0 simply modeled on i386 (below) > > i386 ACPI_BUILD_TABLE_FILE ("etc/acpi/tables") ACPI_BUILD_TABLE_MAX_SIZE (0x200000) n/a > i386 ACPI_BUILD_LOADER_FILE ("etc/table-loader") 0 n/a > i386 ACPI_BUILD_RSDP_FILE ("etc/acpi/rsdp") 0 d70414a5788c, 358774d780ee8 > > microvm ACPI_BUILD_TABLE_FILE ("etc/acpi/tables") ACPI_BUILD_TABLE_MAX_SIZE (0x200000) n/a > microvm "etc/table-loader" 0 no macro for name??? > microvm ACPI_BUILD_RSDP_FILE ("etc/acpi/rsdp") 0 simply modeled on i386 (above) > > (I notice there are some other (optional) fw_cfg blobs too, related TPM, > vmgenid, nvdimm etc, using fw_cfg_add_file() rather than > acpi_add_rom_blob() -- so those are immutable (never regenerated). I > definitely needed this reminder...) most of them are just guest RAM reservations (guest/hose exchange buffer) and "etc/tpm/config" seems to immutable for specific configuration > So, my observations: > > (1) microvm open-codes "etc/table-loader", rather than using the macro > ACPI_BUILD_LOADER_FILE. > > The proposed patch corrects it, which I welcome per se. However, it > should arguably be a separate patch. I found it distracting, in spite of > the commit message highlighting it. I don't insist though, I'm > admittedly rusty on this code. > > > (2) The proposed patch sets "max_size" to ACPI_BUILD_LOADER_MAX_SIZE for > each ACPI_BUILD_LOADER_FILE. Makes sense, upon constructing / reviewing > the above table. > > (I'm no longer sure if tweaking the alignment were the preferable path > forward.) > > Either way, I'd request including the above table in the commit message. > (Maybe drop the "notes" column.) > > > (3) The above 9 invocations are *all* of the acpi_add_rom_blob() > invocations. I find the interface brittle. It's not helpful to have so > many macros for the names and the max sizes. We should have a table with > three entries and -- minimally -- two columns, specifying name and > max_size -- possibly some more call arguments, if such can be extracted. > We should also have an enum type for selecting a row in this table, and > then acpi_add_rom_blob() should be called with an enum constant. > > Of course, talk is cheap. :) > > > (4) When do we plan to introduce a nonzero "max_size" for > ACPI_BUILD_RSDP_FILE ("etc/acpi/rsdp")? > > Is the current zero value a time bomb? it's not likely to go over 4k, but if we enforce max_size!=0 we may set it 4k, which it's aligned to anyways. > Put differently: acpi_add_rom_blob() should be *impossible* to call with > "max_size=0", arguably. *Whenever* we call acpi_add_rom_blob(), we do > that because the blob is resizable (mutable) -- but that also means we > should have a safety margin, does it not? So calling acpi_add_rom_blob() > with "max_size=0" looks self-contradictory. main use-case for using acpi_add_rom_blob() is for mutable blobs, so that all these blobs were transferred during migration to the destination, to ensure that guest sees consistent data set (from source instead of mix of source/dst blobs). Resize came later on, when we got sick of ad-hock (align)/size bumping of "etc/acpi/tables" in configurations where size was on verge of crossing border to the next aligned size and related knobs to keep that mess migratable. > > FWIW, this could be covered by the table proposed in point (3). > > > In total, I don't disagree with the patch (beyond the fact that the new > macro's value doesn't match the commit message), functionally speaking. > However, wrt. readability, I think the patch further complicates the > code. I'd suggest five patches: > > #1 -- use "etc/table-loader" via the proper macro name in "microvm", > > #2 -- rework acpi_add_rom_blob() for using a table of constants + an > enum type, > > #3 -- bump the "max_size" field for ACPI_BUILD_LOADER_FILE, for the > current symptom, > > #4 -- set a nonzero "max_size" for the remaining ACPI_BUILD_RSDP_FILE, > for "future-proofing", > > #5 -- in the new acpi_add_rom_blob() implementation, taking the enum, > assert(max_size != 0). > > (I haven't thought through what this would mean for migration, forward > or backward; I'm just brain-storming.) > > Thanks > Laszlo