All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Why do we have both CONFIG_SOFTMMU and CONFIG_USER_ONLY?
Date: Mon, 7 Dec 2020 11:50:24 +0000	[thread overview]
Message-ID: <CAFEAcA9xLZCmjmBnPUN52wSDYdk2qd14RFXPyU0vWeW53Vg5aA@mail.gmail.com> (raw)
In-Reply-To: <5176c935-2df0-e300-b1cf-67c7014e5d73@suse.de>

On Mon, 7 Dec 2020 at 11:39, Claudio Fontana <cfontana@suse.de> wrote:
>
> As in Subject,
>
> am I understanding correctly that the one or the other is redundant?
>
> Should we keep only one of them?

I think that perhaps the idea at one point was that we
might have a version of linux-user which used a softmmu
(this would allow better control of the guest's view of
its address space, so guest mmap() to fixed addresses
would work better, for instance). But nobody's ever actually
tried to implement that, so I imagine that if we ever did
we'd find that some CONFIG_SOFTMMU and some CONFIG_USER_ONLY
defines were the wrong way around...

thanks
-- PMM


  parent reply	other threads:[~2020-12-07 12:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 11:19 Why do we have both CONFIG_SOFTMMU and CONFIG_USER_ONLY? Claudio Fontana
2020-12-07 11:26 ` Paolo Bonzini
2020-12-07 11:27   ` Claudio Fontana
2020-12-07 11:53     ` Philippe Mathieu-Daudé
2020-12-07 11:50 ` Peter Maydell [this message]
2020-12-07 11:56   ` Claudio Fontana
2020-12-08 18:10     ` Richard Henderson

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=CAFEAcA9xLZCmjmBnPUN52wSDYdk2qd14RFXPyU0vWeW53Vg5aA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=cfontana@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.