From: Marcel Apfelbaum <marcel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Alexander Graf <agraf@suse.de>,
Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] i440/piix and dynamic sysbus check
Date: Wed, 8 Nov 2017 10:57:27 +0200 [thread overview]
Message-ID: <2ec5f251-30d9-bc4b-e3cd-3e31272cfc95@redhat.com> (raw)
In-Reply-To: <CAJ+F1CKWdxAwuZ-QAvT=AhGMrXd+7c8=eBCMMuKPdbK75NDtiQ@mail.gmail.com>
On 07/11/2017 18:40, Marc-André Lureau wrote:
> Hi,
>
> I am working on a TPM CRB device (last sent version:
> https://lists.gnu.org/archive/html/qemu-devel/2017-10/msg02014.html).
> It's a sysbus device, and when starting qemu with i440, I get "Option
> '-device tpm-crb' cannot be handled by this machine".
>
> The check comes from machine_init_notify(), checking that the machine
> has_dynamic_sysbus.
>
> Apparently, q35 supports it. But not i440. If I declare
> has_dynamic_sysbus in piix, the device works fine.
>
> Marcel, could we do something similar to piix to what you did for q35?:
>
Yes, as long as we check all sysbus devices that can't be created
with '-device' have their "cannot_be_insta...yet" flag set.
If Eduardo's series achieves the above is OK.
Thanks,
Marcel
> commit bf8d492405feaee2c1685b3b9d5e03228ed3e47f
> Author: Marcel Apfelbaum <marcel@redhat.com>
> Date: Mon Jun 27 18:38:33 2016 +0300
>
> q35: allow dynamic sysbus
>
> thanks
>
prev parent reply other threads:[~2017-11-08 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:40 [Qemu-devel] i440/piix and dynamic sysbus check Marc-André Lureau
2017-11-07 16:53 ` Eduardo Habkost
2017-11-08 6:54 ` Marc-André Lureau
2017-11-08 8:57 ` Marcel Apfelbaum [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=2ec5f251-30d9-bc4b-e3cd-3e31272cfc95@redhat.com \
--to=marcel@redhat.com \
--cc=agraf@suse.de \
--cc=ehabkost@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.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 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).