From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: Thomas Huth <thuth@redhat.com>, Markus Armbruster <armbru@redhat.com>
Subject: Re: [RFC PATCH 1/2] bulk: Replace !CONFIG_SOFTMMU -> CONFIG_USER_ONLY
Date: Fri, 2 Jun 2023 20:49:59 -0700 [thread overview]
Message-ID: <7913570a-8bf6-2ac9-6869-fab87273742c@linaro.org> (raw)
In-Reply-To: <20230602225811.60152-2-philmd@linaro.org>
On 6/2/23 15:58, Philippe Mathieu-Daudé wrote:
> CONFIG_USER_ONLY is the opposite of CONFIG_SOFTMMU.
> Replace !CONFIG_SOFTMMU negation by the positive form
> which is clearer when reviewing code.
CONFIG_SOFTMMU should be reserved for the actual softmmu tlb, which we *should* be able to
enable for user-only. It is the only way to handle some of our host/guest page size
problems. Further, CONFIG_SOFTMMU should go away as a #define and become a runtime test
(forced to true for system mode). Pie in the sky stuff.
It is quite likely that all uses of CONFIG_SOFTMMU outside of tcg/, accel/tcg/, and random
bits of include/ should only be using CONFIG_USER_ONLY.
r~
next prev parent reply other threads:[~2023-06-03 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 22:58 [RFC PATCH 0/2] bulk: Replace !CONFIG_SOFTMMU and !CONFIG_USER_ONLY Philippe Mathieu-Daudé
2023-06-02 22:58 ` [RFC PATCH 1/2] bulk: Replace !CONFIG_SOFTMMU -> CONFIG_USER_ONLY Philippe Mathieu-Daudé
2023-06-03 3:49 ` Richard Henderson [this message]
2023-06-05 20:29 ` Philippe Mathieu-Daudé
2023-06-05 21:39 ` Richard Henderson
2023-06-02 22:58 ` [RFC PATCH 2/2] bulk: Replace !CONFIG_USER_ONLY -> CONFIG_SOFTMMU Philippe Mathieu-Daudé
2023-06-02 22:59 ` Philippe Mathieu-Daudé
2023-06-02 23:14 ` 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=7913570a-8bf6-2ac9-6869-fab87273742c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).