qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Roman Kagan <rkagan@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
	"Denis V. Lunev" <den@openvz.org>
Subject: [Qemu-devel] vmbus bridge: machine property or device?
Date: Tue, 11 Apr 2017 23:58:16 +0300	[thread overview]
Message-ID: <20170411205813.GA4006@rkaganip.lan> (raw)

While hammering out the VMBus / storage series, we've been struggling to
figure out the best practices solution to the following problem:

VMBus is provided by a vmbus bridge; it appears the most natural to have
it subclassed from SysBusDevice.  There can only be one VMBus in the
VM.

Now the question is how to add it to the system:

1) with a boolean machine property "vmbus" that would trigger the
   creation of the VMBus bridge; its class would have
   ->cannot_instantiate_with_device_add_yet = true


2) with a regular -device option; this would require setting
   ->has_dynamic_sysbus = true for i440fx machines (q35 already have it)


3) anything else


So far we went with 1) but since it's essentially the API the management
layer would have to use we'd like to get it right from the beginning.

Thanks,
Roman.

             reply	other threads:[~2017-04-11 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 20:58 Roman Kagan [this message]
2017-04-12 15:18 ` [Qemu-devel] vmbus bridge: machine property or device? Markus Armbruster
2017-04-12 20:07   ` Eduardo Habkost
2017-04-13 15:15     ` Roman Kagan
2017-04-13 16:44       ` Eduardo Habkost
2017-04-13 16:58         ` Peter Maydell
2017-04-13 18:15           ` Eduardo Habkost
2017-04-13 21:57             ` Peter Maydell
2017-04-13 21:10           ` Roman Kagan
2017-04-13 17:04         ` Roman Kagan
2017-04-13 14:08   ` Roman Kagan

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=20170411205813.GA4006@rkaganip.lan \
    --to=rkagan@virtuozzo.com \
    --cc=den@openvz.org \
    --cc=eyakovlev@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).