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=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 E6BA6C06510 for ; Tue, 2 Jul 2019 09:35:10 +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 BEF2220659 for ; Tue, 2 Jul 2019 09:35:10 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org BEF2220659 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]:51068 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiFBu-00010o-17 for qemu-devel@archiver.kernel.org; Tue, 02 Jul 2019 05:35:10 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:37356) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hiFAX-0008LW-JY for qemu-devel@nongnu.org; Tue, 02 Jul 2019 05:33:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hiFAW-0003ga-L1 for qemu-devel@nongnu.org; Tue, 02 Jul 2019 05:33:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9086) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hiFAW-0003gG-Ew for qemu-devel@nongnu.org; Tue, 02 Jul 2019 05:33:44 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7D5792E95A2; Tue, 2 Jul 2019 09:33:43 +0000 (UTC) Received: from sirius.home.kraxel.org (ovpn-116-96.ams2.redhat.com [10.36.116.96]) by smtp.corp.redhat.com (Postfix) with ESMTP id B2CC65C1A1; Tue, 2 Jul 2019 09:33:37 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id E507311AB5; Tue, 2 Jul 2019 11:33:36 +0200 (CEST) Date: Tue, 2 Jul 2019 11:33:36 +0200 From: Gerd Hoffmann To: Sergio Lopez Message-ID: <20190702093336.zzrzgdg775ca7ptx@sirius.home.kraxel.org> References: <20190701144705.102615-1-slp@redhat.com> <20190701144705.102615-3-slp@redhat.com> <20190702080200.2fzalvwmtcqgtpoq@sirius.home.kraxel.org> <87a7dwygqw.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87a7dwygqw.fsf@redhat.com> User-Agent: NeoMutt/20180716 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Tue, 02 Jul 2019 09:33:43 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: Re: [Qemu-devel] [PATCH v2 2/4] hw/i386: Add an Intel MPTable generator 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: ehabkost@redhat.com, maran.wilson@oracle.com, mst@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Jul 02, 2019 at 10:37:11AM +0200, Sergio Lopez wrote: > > Gerd Hoffmann writes: > > > On Mon, Jul 01, 2019 at 04:47:03PM +0200, Sergio Lopez wrote: > >> Add a helper function (mptable_generate) for generating an Intel > >> MPTable according to version 1.4 of the specification. > >> > >> This is needed for the microvm machine type implementation. > > > > Firmware should do this IMHO (qboot or seabios). > > Microvm does a number of things that are typically done by the firmware, > as a way to reduce boot time. Whenever the firmware or qemu does the initialization shouldn't make that much of a difference. Firmware needs to fetch stuff from fw_cfg, which shouldn't be much overhead when using dma mode. cheers, Gerd