linux-mips
[Top] [All Lists]

Re: 64-bit sysinfo

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: 64-bit sysinfo
From: Trevor Woerner <mips081@vtnet.ca>
Date: Thu, 12 Jun 2003 08:07:59 -0400
Cc: linux-mips@linux-mips.org
In-reply-to: <20030612113520.GA8390@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <200306120659.26501.mips081@vtnet.ca> <20030612113520.GA8390@linux-mips.org>
Reply-to: mips081@vtnet.ca
Sender: linux-mips-bounce@linux-mips.org
User-agent: KMail/1.4.3
On June 12, 2003 07:35 am, Ralf Baechle wrote:
> The kernel has a wrapper for 32-bit code (see sys32_sysinfo) and that
> one seems to look correct to me.
>
> Can you check that your program is actually using the right syscall,
> that is syscall number 4116?  If it's using 5097 it's using the
> native 64-bit syscall which obviously would explain your observation.

Thanks for your (and everyone's suggestions) I'll have a look at this 
today. I put a printk in kernel/proc.c:sys_sysinfo() so that's the one 
being called. I also put another printk in 
arch/mips64/mm/init.c:si_meminfo() (??? i think...) and it was being 
called from 'sys_info()'. I don't remember seeing sys32_sysinfo() but 
I'll look again.

        Trevor

<Prev in Thread] Current Thread [Next in Thread>