From: Leon Alrae <leon.alrae@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>, qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v2 1/2] target-mips: Rework ABIs to allow all required configurations
Date: Mon, 9 Feb 2015 11:30:10 +0000 [thread overview]
Message-ID: <54D89A42.2010004@imgtec.com> (raw)
In-Reply-To: <alpine.DEB.1.10.1412110007550.19155@tp.orcam.me.uk>
On 11/12/2014 00:21, Maciej W. Rozycki wrote:
> Rework the MIPS ABIs and CPU emulations available according to the
> following target list:
>
> - mips|mipsel -- 32-bit CPUs only, system and user emulation mode,
> o32 user ABI,
>
> - mips64|mips64el -- 32-bit and 64-bit CPUs, system and user emulation
> mode, o32 user ABI,
I'm not sure if it's a good idea to change the meaning of linux-user
qemu-mips64 and qemu-mips64el, this will cause unnecessary confusion in
my opinion. I think we’d be better off leaving it consistent across QEMU
versions.
Do we really need MIPS64 executables for o32 ABI for linux-user? They
would merely enable MIPS64 CPUs to run o32 programs. So far we've been
handling this by using 32-bit CPUs (artificial if the real CPU don't
exist), therefore I don't see an issue here. Also I'm concerned that
once we add new executables, it will be difficult to revert that change
later, thus we must be certain that this is the right way to go.
In general I would prefer to avoid changing the user interface and pain
related to breaking people's scripts whenever it's possible.
Regards,
Leon
next prev parent reply other threads:[~2015-02-09 11:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 18:53 [Qemu-devel] [PATCH 0/3] MIPS: GDB register width fix / ABI configuration rework Maciej W. Rozycki
2014-12-10 18:53 ` [Qemu-devel] [PATCH 1/3] target-mips: Add n32/n64 configuration files Maciej W. Rozycki
2014-12-10 19:41 ` Peter Maydell
2014-12-10 20:29 ` Maciej W. Rozycki
2014-12-10 21:30 ` Peter Maydell
2014-12-10 22:14 ` Maciej W. Rozycki
2014-12-10 22:54 ` Peter Maydell
2014-12-10 23:25 ` Maciej W. Rozycki
2014-12-11 9:41 ` Peter Maydell
2014-12-11 14:52 ` Maciej W. Rozycki
2014-12-10 18:53 ` [Qemu-devel] [PATCH 2/3] target-mips: Rework ABIs to allow all required configurations Maciej W. Rozycki
2014-12-10 18:54 ` [Qemu-devel] [PATCH 3/3] target-mips: Set GDB register widths correctly Maciej W. Rozycki
2014-12-11 0:21 ` [Qemu-devel] [PATCH v2 1/2] target-mips: Rework ABIs to allow all required configurations Maciej W. Rozycki
2014-12-12 18:27 ` [Qemu-devel] [PATCH v3 " Maciej W. Rozycki
2015-02-09 11:30 ` Leon Alrae [this message]
2015-02-09 14:09 ` [Qemu-devel] [PATCH v2 " Maciej W. Rozycki
2015-02-09 14:36 ` Peter Maydell
2015-02-11 13:28 ` Maciej W. Rozycki
2014-12-11 0:22 ` [Qemu-devel] [PATCH v2 2/2] target-mips: Set GDB register widths correctly Maciej W. Rozycki
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=54D89A42.2010004@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=macro@linux-mips.org \
--cc=qemu-devel@nongnu.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).