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 lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (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 C9ABAC433F5 for ; Sat, 30 Apr 2022 02:41:09 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.317933.537478 (Exim 4.92) (envelope-from ) id 1nkd2A-00039m-LO; Sat, 30 Apr 2022 02:40:34 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 317933.537478; Sat, 30 Apr 2022 02:40:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nkd2A-00039T-GC; Sat, 30 Apr 2022 02:40:34 +0000 Received: by outflank-mailman (input) for mailman id 317933; Sat, 30 Apr 2022 02:40:34 +0000 Received: from se1-gles-sth1-in.inumbo.com ([159.253.27.254] helo=se1-gles-sth1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1nkd29-00039N-Ux for xen-devel@lists.xenproject.org; Sat, 30 Apr 2022 02:40:33 +0000 Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) by se1-gles-sth1.inumbo.com (Halon) with ESMTPS id e725aba5-c82e-11ec-a405-831a346695d4; Sat, 30 Apr 2022 04:40:32 +0200 (CEST) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:f7]) by mailhost.m5p.com (8.16.1/8.15.2) with ESMTPS id 23U2eKJQ061600 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 29 Apr 2022 22:40:26 -0400 (EDT) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.16.1/8.15.2/Submit) id 23U2eHq2061599; Fri, 29 Apr 2022 19:40:17 -0700 (PDT) (envelope-from ehem) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: e725aba5-c82e-11ec-a405-831a346695d4 Message-Id: From: Elliott Mitchell Cc: Wei Liu Cc: Anthony PERARD Date: Fri, 29 Apr 2022 19:21:53 -0700 Subject: [PATCH v2 0/3] Allow use of JSON in domain configuration files To: xen-devel@lists.xenproject.org While the traditional domain configuration file format works acceptably, I can see uses for having full JSON support. As such add "-j" and "-J" to `xl create` to specify format. The traditional format is the current default. While attempting this, it came up that options for `xl create` aren't in a consistent order. I'm concerned about moving the VNC options apart, but the others have been sorted. Due to one issue in the previous round I ended up examing the dom_info variable in main_create(). The situation there is a bit tangled. There were shadow variables for everything in dom_info. Unfortunately the short-hand serves to confuse, so I believe the appropriate action is to remove the shadows. Appears .dry_run had effectively been deprecated, but not fully removed; as such now fully remove it. Rename everything "format" to "config_format". Elliott Mitchell (3): tools/xl: Sort create command options tools/xl: Use sparse init for dom_info, remove duplicate vars tools/xl: Allow specifying JSON for domain configuration file format tools/xl/xl.h | 6 ++- tools/xl/xl_cmdtable.c | 14 ++--- tools/xl/xl_vmcontrol.c | 114 +++++++++++++++++++++------------------- 3 files changed, 73 insertions(+), 61 deletions(-) -- 2.30.2