From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Zhenwei Pi" <pizhenwei@bytedance.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Fam Zheng" <fam@euphon.net>,
"Eduardo Habkost" <eduardo@habkost.net>
Subject: Re: [PATCH v4 1/8] qdev: Implement qdev_create_fake_machine() for user emulation
Date: Thu, 2 Jan 2025 17:05:47 -0500 [thread overview]
Message-ID: <Z3cNu3ieQ6688QYR@x1n> (raw)
In-Reply-To: <20250102211800.79235-2-philmd@linaro.org>
On Thu, Jan 02, 2025 at 10:17:53PM +0100, Philippe Mathieu-Daudé wrote:
> When a QDev instance is realized, qdev_get_machine() ends up called.
> In the next commit, qdev_get_machine() will require a "machine"
> container to be always present. To satisfy this QOM containers design,
> Implement qdev_create_fake_machine() which creates a fake "machine"
> container for user emulation.
>
> On system emulation, qemu_create_machine() is called from qemu_init().
> For user emulation, since the TCG accelerator always calls
> tcg_init_machine(), we use it to hook our fake machine creation.
>
> Suggested-by: Peter Xu <peterx@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2025-01-02 22:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 21:17 [PATCH v4 0/8] QOM: container_get() removal Philippe Mathieu-Daudé
2025-01-02 21:17 ` [PATCH v4 1/8] qdev: Implement qdev_create_fake_machine() for user emulation Philippe Mathieu-Daudé
2025-01-02 22:05 ` Peter Xu [this message]
2025-01-03 14:24 ` Richard Henderson
2025-01-03 14:37 ` Philippe Mathieu-Daudé
2025-01-02 21:17 ` [PATCH v4 2/8] qdev: Make qdev_get_machine() not use container_get() Philippe Mathieu-Daudé
2025-01-03 14:26 ` Richard Henderson
2025-01-02 21:17 ` [PATCH v4 3/8] qdev: Add machine_get_container() Philippe Mathieu-Daudé
2025-01-03 14:27 ` Richard Henderson
2025-01-02 21:17 ` [PATCH v4 4/8] qdev: Use machine_get_container() Philippe Mathieu-Daudé
2025-01-03 14:29 ` Richard Henderson
2025-01-02 21:17 ` [PATCH v4 5/8] qom: Add object_get_container() Philippe Mathieu-Daudé
2025-01-03 14:29 ` Richard Henderson
2025-01-02 21:17 ` [PATCH v4 6/8] qom: Use object_get_container() Philippe Mathieu-Daudé
2025-01-03 14:30 ` Richard Henderson
2025-01-02 21:17 ` [PATCH v4 7/8] qom: Remove container_get() Philippe Mathieu-Daudé
2025-01-03 14:31 ` Richard Henderson
2025-01-02 21:18 ` [PATCH v4 8/8] system: Inline machine_containers[] in qemu_create_machine_containers() Philippe Mathieu-Daudé
2025-01-03 14:32 ` Richard Henderson
2025-01-09 14:40 ` [PATCH v4 0/8] QOM: container_get() removal Philippe Mathieu-Daudé
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=Z3cNu3ieQ6688QYR@x1n \
--to=peterx@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=fam@euphon.net \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=pizhenwei@bytedance.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).