[RFC v3 PATCH 0/7] ARM: kernel mode NEON in atomic contexts
nicolas.pitre at linaro.org
Tue Oct 15 12:05:48 EDT 2013
On Tue, 15 Oct 2013, Ard Biesheuvel wrote:
> On 15 October 2013 06:01, Nicolas Pitre <nicolas.pitre at linaro.org> wrote:
> > On Sun, 13 Oct 2013, Ard Biesheuvel wrote:
> >> The stack area is allocated by DEFINE_NEON_REGSTACK[_PARTIAL](varname), where
> >> the partial version takes an additional int num_regs indicating how many
> >> registers need to be freed up.
> >> In the !in_interrupt() case, these functions operate as before, and the regstack
> >> is defined to minimal size in this case as it will remain unused anyway. In the
> >> in_interrupt() case, 'num_regs' (or all) NEON registers are stacked/unstacked
> >> using the allocated stack region.
> > Would have been nice to have the stack simply be a NULL pointer when
> > !in_interrupt() or when the number of regs is 0. This would remove the
> > need for a runtime check on !num_regs. I don't see an obvious way to
> > accomplish that right now though.
> We could address both of these issues by implementing Catalin's
> suggestion to reserve per-process vfp_states for both irq and
> softirq context in addition to the ordinary one, but it would waste a
> lot of space imo. What is your take on that?
I agree that this would be rather wasteful. I really like your current
approach of dynamically allocating just the right amount of space on the
stack. I'm not a big fan of statically allocated memory which is
What I meant by my suggestion was something like this:
#define kernel_neon_begin(p) \
__kernel_neon_begin(sizeof((p).qregs) ? &(p).regs : NULL, \
However it seems gcc is not clever enough to optimize the stack usage
away at all in that case which is worse than your current version. So
better forget about this suggestion.
More information about the linux-arm-kernel