From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Konstantin Khlebnikov <koct9i@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Andrey Ryabinin <a.ryabinin@samsung.com>,
Konstantin Khlebnikov <k.khlebnikov@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC] ARM: option for loading modules into vmalloc area
Date: Wed, 19 Nov 2014 16:55:17 +0000 [thread overview]
Message-ID: <20141119165517.GL4042@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKv+Gu8o_-Q5PeFqdQXW=mcHNYxFcLLnvxjq94y-iG8+JUp=9w@mail.gmail.com>
On Wed, Nov 19, 2014 at 05:38:57PM +0100, Ard Biesheuvel wrote:
> Numbers are disambiguated by the f and b suffixes, so they can be
> reused in the same .s file. So as long as you use a strictly numerical
> prefix, you can deal correctly with the case where, for instance,
> do_div() is called twice in the same compilation unit, and still not
> clash with other inline asm
What's not particularly nice though is to hide these in a macro,
which itself may be part of a larger macro or code fragment also
using small numbers.
We probably ought to be a bit more inteligent about how we choose
these numbers inside macros, rather than just randomly picking some
and hoping that they don't clash.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2014-11-19 16:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 16:21 Konstantin Khlebnikov
2014-11-18 17:34 ` Russell King - ARM Linux
2014-11-18 18:13 ` Konstantin Khlebnikov
2014-11-19 13:40 ` Arnd Bergmann
2014-11-19 14:54 ` Ard Biesheuvel
2014-11-19 15:52 ` Konstantin Khlebnikov
2014-11-19 16:02 ` Ard Biesheuvel
2014-11-19 16:07 ` Russell King - ARM Linux
2014-11-19 16:25 ` Ard Biesheuvel
2014-11-19 16:32 ` Konstantin Khlebnikov
2014-11-19 16:38 ` Ard Biesheuvel
2014-11-19 16:55 ` Russell King - ARM Linux [this message]
2014-11-19 16:59 ` Nicolas Pitre
2014-11-19 16:41 ` Russell King - ARM Linux
2014-11-19 16:37 ` Nicolas Pitre
2014-11-19 16:41 ` Ard Biesheuvel
2014-11-19 16:49 ` Russell King - ARM Linux
2014-11-19 16:57 ` Nicolas Pitre
2014-11-19 16:59 ` Russell King - ARM Linux
2014-11-19 17:12 ` Nicolas Pitre
2014-11-19 17:59 ` Ard Biesheuvel
2014-11-19 18:22 ` Nicolas Pitre
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=20141119165517.GL4042@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=a.ryabinin@samsung.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=k.khlebnikov@samsung.com \
--cc=koct9i@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®