All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [RFC] dataplane: IOThreads and writing dataplane-capable code
Date: Thu, 08 May 2014 14:12:06 +0200	[thread overview]
Message-ID: <536B7496.6030903@redhat.com> (raw)
In-Reply-To: <CAJSP0QXijVq+qrzrwKwG8R-5q-d7MbTp7AJMAVsE4WgT3DHXvw@mail.gmail.com>

Il 08/05/2014 13:56, Stefan Hajnoczi ha scritto:
>> > Is dataplane the only user for this now?
> Yes, and neither dataplane (x-data-plane=on) nor IOThread (-object
> iothread,id=<name>) are finalized.
>
> There was a discussion about -object and QOM on the mailing list a
> while back.  We reached the conclusion that -object shouldn't be a
> supported command-line interface, it should be used for testing,
> development, etc.  So an -iothread option still needs to be added.

Actually I think that wasn't the conclusion.

"-object" is a supported command-line interface; we also support 
hotplug/unplug nowadays for it, and the implementation makes QMP 
entirely typesafe unlike netdev_add and device_add.  We're using it for 
iothreads and virtio-rng backends, and we'll add memory backends in 2.1.

However, the agreement was that "QMP methods" are the preferred 
interface to work with objects.  Properties and qom-get/qom-set are not 
the way to build a command-line interface.

Paolo

  reply	other threads:[~2014-05-08 12:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 10:16 [Qemu-devel] [RFC] dataplane: IOThreads and writing dataplane-capable code Stefan Hajnoczi
2014-05-08 11:33 ` Fam Zheng
2014-05-08 11:56   ` Stefan Hajnoczi
2014-05-08 12:12     ` Paolo Bonzini [this message]
2014-05-08 13:08 ` Kevin Wolf
2014-05-08 13:10   ` Paolo Bonzini
2014-05-08 13:18     ` Stefan Hajnoczi
2014-05-08 13:44 ` Dr. David Alan Gilbert
2014-05-08 14:42   ` Stefan Hajnoczi
2014-05-08 18:58     ` Dr. David Alan Gilbert
2014-05-09  8:20       ` Stefan Hajnoczi

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=536B7496.6030903@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    /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.