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=-0.6 required=3.0 tests=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 3955BC432C0 for ; Tue, 3 Dec 2019 14:49:06 +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 03F2420661 for ; Tue, 3 Dec 2019 14:49:06 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="h012i4zH" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 03F2420661 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]:54844 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ic9U9-0003AB-0O for qemu-devel@archiver.kernel.org; Tue, 03 Dec 2019 09:49:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:45468) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ic9On-0000ml-6q for qemu-devel@nongnu.org; Tue, 03 Dec 2019 09:43:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ic9Oe-00072R-Ep for qemu-devel@nongnu.org; Tue, 03 Dec 2019 09:43:26 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:38658 helo=us-smtp-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ic9Oc-0006va-FV for qemu-devel@nongnu.org; Tue, 03 Dec 2019 09:43:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575384197; 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=Ow6wOBzywML2XqkP3hVNuSy1VDpV46IsxVlALzlP/WM=; b=h012i4zHmydBXJbbZ171E3wOhfiZdQnk3me57iaDWvgNalu09v2JAPwrivNCewIPpeu6pN O/FlWVAjYx3F77T4wzFf46yZNm/9rRm7vN6z47+jdCCGCzv/7d6nQN3jnht/5lLufmQuxD BHKFGUxvly+7kfSPjY8Srz0JQSJZw6k= 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-149-EB8nnSrwPkyYBLeE-clrLQ-1; Tue, 03 Dec 2019 09:43:14 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6C8111092D35; Tue, 3 Dec 2019 14:43:13 +0000 (UTC) Received: from localhost (unknown [10.43.2.114]) by smtp.corp.redhat.com (Postfix) with ESMTP id A85D25D6BE; Tue, 3 Dec 2019 14:43:05 +0000 (UTC) Date: Tue, 3 Dec 2019 15:43:03 +0100 From: Igor Mammedov To: Thomas Huth Subject: Re: [PATCH 2/2] Add -mem-shared option Message-ID: <20191203154303.035c33b3@redhat.com> In-Reply-To: <1ff4cc6a-0ec8-96ff-1e39-e682429852e4@redhat.com> References: <20191128141518.628245-1-marcandre.lureau@redhat.com> <20191128141518.628245-3-marcandre.lureau@redhat.com> <20191128172807.788e6aeb@redhat.com> <20191129110703.2b15c541@redhat.com> <04dadf85-cd35-fd37-9642-8087cba625bd@redhat.com> <20191129131652.6683b769@redhat.com> <528bb183-3d44-e541-8765-9c0e01f23157@redhat.com> <20191202083948.3e8bb134@redhat.com> <20191202210057.GQ14595@habkost.net> <1ff4cc6a-0ec8-96ff-1e39-e682429852e4@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: EB8nnSrwPkyYBLeE-clrLQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 207.211.31.120 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: Eduardo Habkost , libvir-list@redhat.com, QEMU , =?UTF-8?B?TWFyYy1BbmRyw6k=?= Lureau , Stefan Hajnoczi , Paolo Bonzini , Richard Henderson Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, 3 Dec 2019 09:56:15 +0100 Thomas Huth wrote: > On 02/12/2019 22.00, Eduardo Habkost wrote: > > On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote: > >> On Fri, 29 Nov 2019 18:46:12 +0100 > >> Paolo Bonzini wrote: > >> > >>> On 29/11/19 13:16, Igor Mammedov wrote: > >>>> As for "-m", I'd make it just an alias that translates > >>>> -m/mem-path/mem-prealloc > >>> > >>> I think we should just deprecate -mem-path/-mem-prealloc in 5.0. CCing > >>> Thomas as mister deprecation. :) > >> > >> I'll add that to my series > > > > Considering that the plan is to eventually reimplement those > > options as syntactic sugar for memory backend options (hopefully > > in less than 2 QEMU releases), what's the point of deprecating > > them? > > Well, it depends on the "classification" [1] of the parameter... > > Let's ask: What's the main purpose of the option? > > Is it easier to use than the "full" option, and thus likely to be used > by a lot of people who run QEMU directly from the CLI? In that case it > should stay as "convenience option" and not be deprecated. > > Or is the option merely there to give the upper layers like libvirt or > some few users and their scripts some more grace period to adapt their > code, but we all agree that the options are rather ugly and should > finally go away? Then it's rather a "legacy option" and the deprecation > process is the right way to go. Our QEMU interface is still way > overcrowded, we should try to keep it as clean as possible. After switching to memdev for main RAM, users could use relatively short global options -global memory-backend.prealloc|share=on and -global memory-backend-file.mem-path=X|prealloc|share=on instead of us adding and maintaining slightly shorter -mem-shared/-mem-path/-mem-prealloc > Thomas > > > [1] Using the terms from: > https://www.youtube.com/watch?v=Oscjpkns7tM&t=8m