Hi Adrian,
On 23/7/20 8:03 pm, John Paul Adrian Glaubitz wrote:
Hello!
Michael and I have been working on SECCOMP in SuperH and successfully added
the missing pieces yesterday [1].
We're now looking into what needs to be done for m68k and I have noticed that
syscall_trace_enter and syscall_trace_leave - which needs to be touched for
SECCOMP support - are available on ColdFire and non-MMU targets for m68k.
Is there a particular reason for that? Looking at 68000/entry.S, I can see
that both functions are invoked [2] so I'm not sure why they are built
for CONFIG_COLDFIRE and !CONFIG_MMM only.
Any ideas?
I am late to the party on this.
But the reason is historical more than anything else.
The time that m68knommu, which included ColdFire, spent as its own architecture
directory (arch/m68knommu) led to a few things like this diverging.
There is not technical reason.
Regards
Greg
Adrian
[1] https://marc.info/?l=linux-sh&m=159546012829989&w=2
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/m68k/68000/entry.S
