On Tue, Sep 20, 2016 at 11:39:35PM -0700, Andy Lutomirski wrote:
> > And the ia64 entry code has some similar language:
> >
> > /*
> > * Invoke schedule_tail(task) while preserving in0-in7,
> > which may be needed
> > * in case a system call gets r
On Sep 20, 2016 5:25 PM, "Josh Poimboeuf" wrote:
>
> On Tue, Sep 20, 2016 at 09:10:55PM -0400, Brian Gerst wrote:
> > Dropping asmlinkage from schedule_tail() would be a better option if
> > possible.
>
> My understanding is that it's still needed for ia64. AFAICT, ia64
> relies on schedule_tail
On Tue, Sep 20, 2016 at 10:25:16PM -0500, Josh Poimboeuf wrote:
> On Tue, Sep 20, 2016 at 09:10:55PM -0400, Brian Gerst wrote:
> > Dropping asmlinkage from schedule_tail() would be a better option if
> > possible.
>
> My understanding is that it's still needed for ia64. AFAICT, ia64
> relies on
On Tue, Sep 20, 2016 at 09:10:55PM -0400, Brian Gerst wrote:
> Dropping asmlinkage from schedule_tail() would be a better option if possible.
My understanding is that it's still needed for ia64. AFAICT, ia64
relies on schedule_tail() having the syscall_linkage function attribute.
>From the gcc ma
On Tue, Sep 20, 2016 at 4:02 PM, Josh Poimboeuf wrote:
> Thanks to all the recent x86 entry code refactoring, most tasks' kernel
> stacks start at the same offset right below their saved pt_regs,
> regardless of which syscall was used to enter the kernel. That creates
> a nice convention which ma
5 matches
Mail list logo
