From: "Jose R. Ziviani" <jziviani@suse.de>
To: Thomas Huth <thuth@redhat.com>
Cc: pbonzini@redhat.com, cfontana@suse.de,
richard.henderson@linaro.org, qemu-devel@nongnu.org,
kraxel@redhat.com
Subject: Re: [PATCH 0/1]
Date: Wed, 21 Jul 2021 10:34:11 -0300 [thread overview]
Message-ID: <YPgiU5JbzupGG6B7@pizza> (raw)
In-Reply-To: <ce1bda4a-e9e8-ec43-31ef-9ef3a58a16c1@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
On Wed, Jul 21, 2021 at 07:24:02AM +0200, Thomas Huth wrote:
> On 21/07/2021 00.13, Jose R. Ziviani wrote:
> > Hello!
> >
> > This patch gives the ability to build TCG builtin even if
> > --enable-modules is selected. This is useful to have a base
> > QEMU with TCG native product but still using the benefits of
> > modules.
>
> Could you please elaborate why this is required? Did you see a performance
> improvement? Or is there another problem?
Hello Thomas,
Please, disconsider this patch. There's a more general discussion about
modules happening here:
https://lists.nongnu.org/archive/html/qemu-devel/2021-07/msg00632.html
A more general solution may be required to actually give us a
fine-grained control on modules.
The case is to allow us to generate customized QEMU packages attending
different user needs.
Thank you very much!!
Jose
>
> Thomas
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-07-21 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 22:13 [PATCH 0/1] Jose R. Ziviani
2021-07-20 22:13 ` [PATCH 1/1] modules: Option to build native TCG with --enable-modules Jose R. Ziviani
2021-07-21 5:24 ` [PATCH 0/1] Thomas Huth
2021-07-21 13:34 ` Jose R. Ziviani [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=YPgiU5JbzupGG6B7@pizza \
--to=jziviani@suse.de \
--cc=cfontana@suse.de \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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 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).