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 Received: from lists1p.gnu.org (lists1p.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A4C87C61DD6 for ; Fri, 4 Sep 2026 11:01:30 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1x2Rfb-0008QR-0r; Fri, 04 Sep 2026 07:01:20 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1x2RfZ-0008Pa-ET for qemu-devel@nongnu.org; Fri, 04 Sep 2026 07:01:17 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1x2RfX-0007xU-VD for qemu-devel@nongnu.org; Fri, 04 Sep 2026 07:01:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1788519675; 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: in-reply-to:in-reply-to:references:references; bh=G8lPvK6vwLltvvSyBubg/zHHrGlAgiIczm/xHPn13hU=; b=LzWirY2MpzRIpi7M+avhgvOyUKrxA0/v8wQJQ+zY0XoJX24kvgKbBHXLOeN4+wOU416gmH w4jyYQzWXp2uYZsc9DAgtPbydejW6rVv4fOtpZ+IoIqd27THz2cXpLZFqb9M9tiWu/hFRs OM+2Ja+ulww6LodaJwVJKmSWAiCyRzA= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-387-QngRg38EOBO-6sTpQ8V5hw-1; Fri, 04 Sep 2026 07:01:08 -0400 X-MC-Unique: QngRg38EOBO-6sTpQ8V5hw-1 X-Mimecast-MFC-AGG-ID: QngRg38EOBO-6sTpQ8V5hw_1788519667 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 08A6E19773CA; Fri, 4 Sep 2026 11:01:07 +0000 (UTC) Received: from blackfin.pond.sub.org (unknown [10.44.22.5]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 4159118005AC; Fri, 4 Sep 2026 11:01:06 +0000 (UTC) Received: by blackfin.pond.sub.org (Postfix, from userid 1000) id 68E9121E6A04; Fri, 04 Sep 2026 13:01:03 +0200 (CEST) From: Markus Armbruster To: Peter Maydell Cc: luoyonggang@gmail.com, Daniel P. =?utf-8?Q?Berrang=C3=A9?= , Pierrick Bouvier , qemu-devel@nongnu.org, anjo@rev.ng, Daniel Henrique Barboza , philmd@oss.qualcomm.com, Paolo Bonzini , Richard Henderson Subject: Re: [PATCH 00/47] single-binary: implement dynamic filtering for QOM types In-Reply-To: (Peter Maydell's message of "Fri, 4 Sep 2026 10:13:04 +0100") References: <20260828225901.367438-1-pierrick.bouvier@oss.qualcomm.com> <4b4f77ee-21e9-405e-a1da-21506afa1c5b@oss.qualcomm.com> Date: Fri, 04 Sep 2026 13:01:03 +0200 Message-ID: <87ld9h8emo.fsf@pond.sub.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Received-SPF: pass client-ip=170.10.129.124; envelope-from=armbru@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: 12 X-Spam_score: 1.2 X-Spam_bar: + X-Spam_report: (1.2 / 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Peter Maydell writes: > I was wondering if maybe one way to approach that is some > "disambiguation" syntax on the machine name; so one could write > "-machine aarch64:virt" vs "-machine riscv64:virt" (or whatever) to > disambiguate when just "-machine virt" would be ambiguous; but if > there's only one machine of that name then just "-machine foo" would > work. That extends nicely to truly heterogenous machine names: > "-machine my-mixed-machine" wouldn't need the user to explicitly > give it a -target option or otherwise say that it includes aarch64 > and microblaze CPUs. (We'd probably need to put something in to > prevent future machine name clashes across targets, so that the > only clashes are our existing legacy ones.) Do we need new syntax? Rename the clashing machine types, keeping the old name as alias. When getting a machine by name, require the name to be unambiguous. > This rests on the assumption that the only thing we need to > disambiguate is machine names, i.e. there aren't multiple > targets with user-facing (i.e. not easily renameable) device > names that are shared.