From: Aurelien Jarno <aurelien@aurel32.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 2/5] softmmu templates: optionally pass CPUState to memory access functions
Date: Fri, 24 Aug 2012 20:53:48 +0200 [thread overview]
Message-ID: <20120824185348.GH1687@hall.aurel32.net> (raw)
In-Reply-To: <5037CB54.9030800@suse.de>
On Fri, Aug 24, 2012 at 08:43:32PM +0200, Andreas Färber wrote:
> Am 24.08.2012 20:05, schrieb Aurelien Jarno:
> > On Fri, Aug 24, 2012 at 05:52:29PM +0200, Andreas Färber wrote:
> >> Not opposed to changing the argument order, but given that we're inches
> >> away from v1.2 (in Hard Freeze), it might be better to first get AREG0
> >> as first argument working for your favorite hosts as a bugfix and then
> >> do any larger optimization for v1.3.
> >
> > It's what I tried to do first, but I don't think it is realistic to use
> > such a code for v1.2, it is complex to support all cases, and thus
> > likely full of bugs. Maybe we should simply disable ARM and MIPS support
> > for this release.
>
> Depends on what you mean with "disable"? Adding an #error would hurt our
> arm build just like earlier the ppc build, and I would hope from my last
> testing that the problems would only affect the AREG0 targets,
> especially not ARM on ARM (or MIPS on MIPS).
>
I mean basically not building qemu-system-{alpha,i386,x86_64,or32,sparc,
sparc64,xtensa,ppc,ppc64} on arm and mips hosts.
> Aborting at runtime, only when really unsupported, would seem better.
What's the point of providing non working binaries, beside getting bug
reports?
>
> I had taken a look at tcg/arm/ shortly after having fixed ppc (seeing
> that there was a similar TODO or FIXME) but got distracted by other
> projects. And your remarks wrt stack sound a bit frightening now. ;)
> @Peter, have you looked into tcg/arm/ AREG0 support?
>
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2012-08-24 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 22:24 [Qemu-devel] [PATCH 2/5] softmmu templates: optionally pass CPUState to memory access functions Blue Swirl
2012-08-24 15:05 ` Aurelien Jarno
2012-08-24 15:33 ` malc
2012-08-24 15:35 ` malc
2012-08-24 15:52 ` Andreas Färber
2012-08-24 16:26 ` malc
2012-08-24 18:20 ` Andreas Färber
2012-08-24 18:05 ` Aurelien Jarno
2012-08-24 18:43 ` Andreas Färber
2012-08-24 18:53 ` Aurelien Jarno [this message]
2012-08-25 9:18 ` Blue Swirl
2012-08-25 12:56 ` Aurelien Jarno
2012-08-24 23:01 ` Peter Maydell
2012-08-25 9:52 ` Blue Swirl
2012-09-20 11:46 ` Alexander Graf
2012-08-25 12:53 ` Aurelien Jarno
2012-08-25 23:28 ` Peter Maydell
2012-08-26 1:03 ` Peter Maydell
2012-08-25 9:05 ` Blue Swirl
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=20120824185348.GH1687@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=blauwirbel@gmail.com \
--cc=peter.maydell@linaro.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).