From: Dave Martin <dave.martin@linaro.org> To: Russell King - ARM Linux <linux@arm.linux.org.uk> Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com> Subject: Re: [PATCH 0/0] RFC: ARM: Thumb-2: Symbol manipulation macros for function body copying Date: Wed, 12 Jan 2011 10:55:35 -0600 [thread overview] Message-ID: <AANLkTi=OtfO8xxT_8X2XzePhvYG0Zdd3V5mX9-5tRed_@mail.gmail.com> (raw) In-Reply-To: <20110112161151.GB18833@n2100.arm.linux.org.uk> On Wed, Jan 12, 2011 at 10:11 AM, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote: > On Wed, Jan 12, 2011 at 10:00:25AM -0600, Dave Martin wrote: >> omap provides some infrastructure for both allocating SRAM space and >> doing the copy, using omap_sram_push() and friends. So I wasn't sure >> what the correct level of abstraction was for the new helpers. >> Certainly, providing a sort of "function memcpy" macro like your >> copy_fn_to_sram makes sense. > > It'd just be a matter of splitting the copying out of omap_sram_push(). > >> I think this should still be safe from a type system perspective: >> providing the "blind" type casts using asm() appear somewhere in >> the execution flow C shouldn't make silly assumptions even if Linux >> ends up enabling multifile optimisation sometime in the future. > > Yes. The only thing that is missing from my version is the > flush_icache_range() which should also be there. > >> > Used by: >> > extern void my_func(int foo); >> > extern int my_func_size; >> >> Potentially, we could define, an extra assembler macro to complement >> ENDPROC() which records the size of a function automatically. What do >> you think? Sure -- we shouldn't change ENDPROC() itself, but we could have, say, and ENDPROC_SZ() macro which people should use strictly when they know they need it. > > That would pad the code out with a fair number of additional integers. > That's probably not a good idea. > >> The model used in the omap code is to copy some functions into SRAM >> ahead of time and stash the pointers away to be called later: for that >> model, it's not so useful to have something like call_my_func >> directly. Also, I wasn't sure whether conflating other functionality >> such as cache flushing into the new macros would be a good idea -- is >> might be cleaner and more maintainable, but might result in less >> efficient usage. Any thoughts? > > My example was only that - an example. You can also use it in the > way you describe too: > > to = omap_sram_push(size); > _omap_sram_reprogram_clock = copy_fn_to_sram(to, > omap1_sram_reprogram_clock, size); > > and it'll also ensure type-safety between the omap1_sram_reprogram_clock > and _omap_sram_reprogram_clock symbols, which the current code doesn't > do. > Ah, OK -- I'd interpreted call_my_func() as part of the API, rather than a usage example. I'll have a think and update the patch. Cheers ---Dave -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: dave.martin@linaro.org (Dave Martin) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/0] RFC: ARM: Thumb-2: Symbol manipulation macros for function body copying Date: Wed, 12 Jan 2011 10:55:35 -0600 [thread overview] Message-ID: <AANLkTi=OtfO8xxT_8X2XzePhvYG0Zdd3V5mX9-5tRed_@mail.gmail.com> (raw) In-Reply-To: <20110112161151.GB18833@n2100.arm.linux.org.uk> On Wed, Jan 12, 2011 at 10:11 AM, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote: > On Wed, Jan 12, 2011 at 10:00:25AM -0600, Dave Martin wrote: >> omap provides some infrastructure for both allocating SRAM space and >> doing the copy, using omap_sram_push() and friends. ?So I wasn't sure >> what the correct level of abstraction was for the new helpers. >> Certainly, providing a sort of "function memcpy" macro like your >> copy_fn_to_sram makes sense. > > It'd just be a matter of splitting the copying out of omap_sram_push(). > >> I think this should still be safe from a type system perspective: >> providing the "blind" type casts using asm() appear somewhere in >> the execution flow C shouldn't make silly assumptions even if Linux >> ends up enabling multifile optimisation sometime in the future. > > Yes. ?The only thing that is missing from my version is the > flush_icache_range() which should also be there. > >> > Used by: >> > extern void my_func(int foo); >> > extern int my_func_size; >> >> Potentially, we could define, an extra assembler macro to complement >> ENDPROC() which records the size of a function automatically. ?What do >> you think? Sure -- we shouldn't change ENDPROC() itself, but we could have, say, and ENDPROC_SZ() macro which people should use strictly when they know they need it. > > That would pad the code out with a fair number of additional integers. > That's probably not a good idea. > >> The model used in the omap code is to copy some functions into SRAM >> ahead of time and stash the pointers away to be called later: for that >> model, it's not so useful to have something like call_my_func >> directly. ?Also, I wasn't sure whether conflating other functionality >> such as cache flushing into the new macros would be a good idea -- is >> might be cleaner and more maintainable, but might result in less >> efficient usage. ?Any thoughts? > > My example was only that - an example. ?You can also use it in the > way you describe too: > > ? ? ? ?to = omap_sram_push(size); > ? ? ? ?_omap_sram_reprogram_clock = copy_fn_to_sram(to, > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?omap1_sram_reprogram_clock, size); > > and it'll also ensure type-safety between the omap1_sram_reprogram_clock > and _omap_sram_reprogram_clock symbols, which the current code doesn't > do. > Ah, OK -- I'd interpreted call_my_func() as part of the API, rather than a usage example. I'll have a think and update the patch. Cheers ---Dave
next prev parent reply other threads:[~2011-01-12 16:55 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-12 0:02 [PATCH 0/0] RFC: ARM: Thumb-2: Symbol manipulation macros for function body copying Dave Martin 2011-01-12 0:02 ` Dave Martin 2011-01-12 0:02 ` [PATCH 1/1] " Dave Martin 2011-01-12 0:02 ` Dave Martin 2011-01-12 9:32 ` [PATCH 0/0] RFC: " Russell King - ARM Linux 2011-01-12 9:32 ` Russell King - ARM Linux 2011-01-12 16:00 ` Dave Martin 2011-01-12 16:00 ` Dave Martin 2011-01-12 16:11 ` Russell King - ARM Linux 2011-01-12 16:11 ` Russell King - ARM Linux 2011-01-12 16:55 ` Dave Martin [this message] 2011-01-12 16:55 ` Dave Martin
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='AANLkTi=OtfO8xxT_8X2XzePhvYG0Zdd3V5mX9-5tRed_@mail.gmail.com' \ --to=dave.martin@linaro.org \ --cc=j-pihet@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ /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: linkBe 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.