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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1BDBC433EF for ; Thu, 30 Sep 2021 00:33:36 +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 3DD5F61288 for ; Thu, 30 Sep 2021 00:33:36 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 3DD5F61288 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=nongnu.org Received: from localhost ([::1]:52874 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mVk11-0000Rj-1o for qemu-devel@archiver.kernel.org; Wed, 29 Sep 2021 20:33:35 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:34532) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVjzc-00081d-6o for qemu-devel@nongnu.org; Wed, 29 Sep 2021 20:32:08 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]:24781) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mVjza-0006WR-9R for qemu-devel@nongnu.org; Wed, 29 Sep 2021 20:32:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1632961925; 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=8Sg16EQ/ELyLyN1NzQmcc4v/dFLkTNZ1/8al+M03WqI=; b=RmXR/txj6iJuog37jaEhXoWTchTbPHBPibqk0tkj+f/wxAyhlBKY2ofH7763TwEY+jJfX5 XGVgPFQ0pyrkZBprU21pGoy7WMl8kDT/Iqa5dpUPYr6JGlvv99i9jAmusTsp+QOfr8qMo4 6R2Peo+8Uc6nzThrTVUzR2knpNQOkTY= Received: from mail-vs1-f70.google.com (mail-vs1-f70.google.com [209.85.217.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-9-UFoW4oxrOCOkKMRBrz4t4w-1; Wed, 29 Sep 2021 20:32:03 -0400 X-MC-Unique: UFoW4oxrOCOkKMRBrz4t4w-1 Received: by mail-vs1-f70.google.com with SMTP id s22-20020a67d096000000b002d82ca46270so5472vsi.8 for ; Wed, 29 Sep 2021 17:32:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8Sg16EQ/ELyLyN1NzQmcc4v/dFLkTNZ1/8al+M03WqI=; b=0z4AgtJvXtA2JMfPBAPbFzrEevF0Pg9PW387JQY3ZbkeMS/DWNzVT6SPJ6ySnsMnKk EhSKvSca/TST+zCi54jXsgE/AZ0uNY+eUFYP3eHPNRj1AkBGuwX3bvWsDuGZtvfwRHP0 438YEOvUzxOZf5CuPHLpXCR9UfndPx11roaLjcbolmaPdec6bYgcjNSYJApCJRn6bFNP by0/DtcLU8laJHnzWtUwvt1TWz2swThl2nepbxgJddqyAkSn/HZuvbifvMvFWcvIXnHz 3uPmYICC4QmIQ6XN7QyP5rxOCUzpaQvSJb3BXkRzuCyse/CaPLEAGueEKatsK0oNDO0T KMYw== X-Gm-Message-State: AOAM530GZux1AfcKz+b/77cw37vI0SJ37r1PxVmxhY87Y5wSSTyhRPfh JG7ZFY4ruBs7gslnccBLLtaagfzS7ZDKLGEKNAlcaUTztBhQmAHsHHPdbsXCEo1uRHd5G4Sqm9d moL/bgrrJUjTLI6ecD4SWKYZm2h8mAQE= X-Received: by 2002:a67:f685:: with SMTP id n5mr1130634vso.31.1632961923216; Wed, 29 Sep 2021 17:32:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzHRxI0dsMj8sPRrNZf/Nop9a7iVft86T7pde9Y3IgjVqkGFnlIfhe4tKcRhDnRrKZc4Tos6r4KrexBrA4fci4= X-Received: by 2002:a67:f685:: with SMTP id n5mr1130621vso.31.1632961923063; Wed, 29 Sep 2021 17:32:03 -0700 (PDT) MIME-Version: 1.0 References: <3a2b391c-df8e-96ef-570e-4dde6002241e@greensocs.com> In-Reply-To: <3a2b391c-df8e-96ef-570e-4dde6002241e@greensocs.com> From: John Snow Date: Wed, 29 Sep 2021 20:31:52 -0400 Message-ID: Subject: Re: QAPI sync meeting To: Damien Hedde Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jsnow@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: multipart/alternative; boundary="0000000000005b3b9605cd2b930a" Received-SPF: pass client-ip=170.10.129.124; envelope-from=jsnow@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, HTML_MESSAGE=0.001, 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=ham 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: =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= , Markus Armbruster , qemu-devel Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" --0000000000005b3b9605cd2b930a Content-Type: text/plain; charset="UTF-8" On Wed, Sep 29, 2021 at 9:52 AM Damien Hedde wrote: > > > On 9/27/21 18:55, John Snow wrote: > > Hiya, > > > > I'd like to propose that at least the three of us arrange a time to have > > a meeting where we discuss our plans and ideas for QAPI going forward, > > including rust, python, and golang extensions to the QAPI generator, > > what we hope to accomplish with those projects, and so on. > > > > What I am hoping to get out of this for myself is a high-level overview > > of people's plans for QAPI and to produce some notes on those plans so > > that I can have a reference that we've all acknowledged as roughly > > accurate to be able to keep the community's design goals for QAPI in > > mind as I continue my own development. Ultimately, I'd like some kind of > > rough draft of a "QAPI roadmap". > > > > I know there was a rust meetup during KVM Forum, but I was unable to > > attend due to the timing. I'd like to expand the focus a little more > > broadly to QAPI in general and discuss our "personal" roadmaps, goals, > > queued work, etc so that we can collaboratively formulate a broader > > vision of our work. > > > > I'm posting to qemu-devel in case anyone else has an interest in this > > area and would like to eavesdrop or share opinions, but we should > > probably come up with an agenda first. So: > > > > I would be interested too. > > My current topic of interest is somewhat distant (roughly: "remote" > machine assembly) but I would like to better understand the QAPI roadmap. > > The area that greensocs is working on is of direct interest to me as well: I want 100% QEMU configuration via QMP. (And then either I drop the command line, or re-architect the CLI such that it is 100% a mapping onto equivalent QMP, or ... something. It's been a somewhat hot topic at times, but 100% QMP configuration seems like where the meat of the work is, anyway. Everything after that is kinda just 'details'.) > -- > Damien > > --0000000000005b3b9605cd2b930a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Sep 29, 2021 at 9:52 AM Damie= n Hedde <damien.hedde@gree= nsocs.com> wrote:


On 9/27/21 18:55, John Snow wrote:
> Hiya,
>
> I'd like to propose that at least the three of us arrange a time t= o have
> a meeting where we discuss our plans and ideas for QAPI going forward,=
> including rust, python, and golang extensions to the QAPI generator, <= br> > what we hope to accomplish with those projects, and so on.
>
> What I am hoping to get out of this for myself is a high-level overvie= w
> of people's plans for QAPI and to produce some notes on those plan= s so
> that I can have a reference that we've all acknowledged as roughly=
> accurate to be able to keep the community's design goals for QAPI = in
> mind as I continue my own development. Ultimately, I'd like some k= ind of
> rough draft of a "QAPI roadmap".
>
> I know there was a rust meetup during KVM Forum, but I was unable to <= br> > attend due to the timing. I'd like to expand the focus a little mo= re
> broadly to QAPI in general and discuss our "personal" roadma= ps, goals,
> queued work, etc so that we can collaboratively formulate a broader > vision of our work.
>
> I'm posting to qemu-devel in case anyone else has an interest in t= his
> area and would like to eavesdrop or share opinions, but we should
> probably come up with an agenda first. So:
>

I would be interested too.

My current topic of interest is somewhat distant (roughly: "remote&quo= t;
machine assembly) but I would like to better understand the QAPI roadmap.

The area that greensocs is working on = is of direct interest to me as well: I want 100% QEMU configuration via QMP= .

(And then either I drop the command line, or re-= architect the CLI such that it is 100% a mapping onto equivalent QMP, or ..= . something. It's been a somewhat hot topic at times, but 100% QMP conf= iguration seems like where the meat of the work is, anyway. Everything afte= r that is kinda just 'details'.)
=C2=A0
--
Damien

--0000000000005b3b9605cd2b930a--