All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: jsnow@redhat.com
Cc: damien.hedde@greensocs.com, kwolf@redhat.com,
	berrange@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
	marcandre.lureau@redhat.com, pbonzini@redhat.com
Subject: Re: Invitation: QAPI Sync meeting @ Thu Oct 7, 2021 9am - 10am (EDT) (qemu-devel@nongnu.org)
Date: Thu, 07 Oct 2021 14:36:27 +0200	[thread overview]
Message-ID: <87a6jlggfo.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <00000000000093852d05cd8d38f6@google.com> (jsnow@redhat.com's message of "Mon, 04 Oct 2021 21:01:46 +0000")

Thursday crept up on me...  I just noticed we haven't gotten around to
circulate a one-page summary of the topics of interest.  In the hope
that late & crude is better than never, here's mine.  If I misunderstand
you, please be lenient, and correct me on the call.

= Technical =

Marc-André is interested in language bindings, Rust in particular.  He
explored this some.  There are problems.

Kevin and Markus are interested in CLI QAPIfication, and QAPI/QOM
integration.

Daniel is interested in 100% pure QAPI-based QEMU configuration.

For proper CLI QAPIfication, the traditional / "human-friendly"syntax
should become a wrapper around "machine-friendly", just like HMP is /
should be a wrapper around QMP.  He's exploring techniques that let us
avoid writing these wrappers completely by hand.

The external QOM interfaces are not specified in QAPI, and therefore not
covered by QAPI introspection.  QAPI/QOM integration could fix that, and
also generate QOM boilerplate.

The way -device / device_add is implemented defeats type checking.  If
we fix that, users that get the types wrong break.  Libvirt does.

John and Markus are interested in making the QAPI code generator easier
to maintain.  Type hints, in particular

Markus is interested in extending QAPI special feature flags and -compat
beyond "deprecated".

= Process =

How can we make the merging of non-trivial QAPI language work less
painfully slow?



      reply	other threads:[~2021-10-07 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 21:01 Invitation: QAPI Sync meeting @ Thu Oct 7, 2021 9am - 10am (EDT) (qemu-devel@nongnu.org) jsnow
2021-10-07 12:36 ` Markus Armbruster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a6jlggfo.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=damien.hedde@greensocs.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.