From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors (v6)
Date: Thu, 29 Jul 2010 21:28:56 +0200 [thread overview]
Message-ID: <20100729192855.GA4298@elf.ucw.cz> (raw)
In-Reply-To: <201007291313.29923.siarhei.siamashka@nokia.com>
On Thu 2010-07-29 13:13:29, Siarhei Siamashka wrote:
> On Wednesday 28 July 2010 09:06:49 ext Pavel Machek wrote:
> > On Mon 2010-07-19 22:02:12, Linus Walleij wrote:
> > > 2010/7/19 Kirill A. Shutemov <kirill@shutemov.name>:
> > > > Why do we need this? Why do not just fix broken programs?
> > >
> > > People tend to use some third-party precompiled binaries, some of
> > > them compiled with a compiler using SWP.
> >
> > Why not just let the cpu emulate it? It surely will be faster...?
>
> IMHO, being able to identify the usage of SWP instructions and fix bad
> programs eventually (by spamming the said third-party programs bugtrackers) is
> a good enough reason.
Why do we need _emulation_ for that?
Either you care about compatibility, then you let the CPU emulate SWP,
or you want to fix your userspace, so you turn off SWP emulation and
see what breaks.
I believe emulation just to annoy users into submitting bugreports is
serious overengineering.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-07-29 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 18:02 [PATCH] ARM: Add SWP/SWPB emulation for ARMv7 processors (v6) Leif Lindholm
2010-07-19 19:49 ` Kirill A. Shutemov
2010-07-19 20:02 ` Linus Walleij
2010-07-19 21:26 ` Kirill A. Shutemov
2010-07-28 6:06 ` Pavel Machek
2010-07-29 10:13 ` Siarhei Siamashka
2010-07-29 19:28 ` Pavel Machek [this message]
2010-07-30 10:04 ` Siarhei Siamashka
2010-07-31 10:52 ` Russell King - ARM Linux
2010-07-31 11:29 ` Russell King - ARM Linux
2010-08-02 18:45 ` Leif Lindholm
2010-08-03 19:42 ` Jamie Lokier
2010-07-20 9:12 ` Catalin Marinas
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=20100729192855.GA4298@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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.