linux-kernel - RE: [PATCH] Unicore architecture patch review, part 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <017801cb9752$79a48a50$6ced9ef0$@mprc.pku.edu.cn>
Date:	Thu, 9 Dec 2010 11:37:58 +0800
From:	"Guan Xuetao" <guanxuetao@...c.pku.edu.cn>
To:	"'Arnd Bergmann'" <arnd@...db.de>
Cc:	<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] Unicore architecture patch review, part 2



> -----Original Message-----
> From: linux-arch-owner@...r.kernel.org [mailto:linux-arch-
> owner@...r.kernel.org] On Behalf Of Arnd Bergmann
> Sent: Wednesday, December 08, 2010 8:54 PM
> To: Guan Xuetao
> Cc: linux-arch@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH] Unicore architecture patch review, part 2
> 
> On Wednesday 08 December 2010, Guan Xuetao wrote:
> 
> > > > @@ -0,0 +1,390 @@
> > > > +/* 0 */		CALL(sys_restart_syscall)
> > > > +		CALL(sys_exit)
> > > > +		CALL(sys_fork_wrapper)
> > > > +		CALL(sys_read)
> > > > +		CALL(sys_write)
> > > > +/* 5 */		CALL(sys_open)
> > > > +		CALL(sys_close)
> > >
> > > When you start using the generic unistd.h file, you can also replace
> > > this table with something like arch/tile/kernel/sys.c.
> > Well. I will use the generic unistd.h in UniCore-64 version.
> 
> I thought you had agreed to break ABI compatibility with your existing
code
> base and use the generic ABI everywhere.
> 
> Did I misunderstand you or did you make up your mind since then?
> 
We do define new 32-bit ABI work at present, and I will use generic unistd
in new ABI.
But existing machines must be maintained, so many codes need remain
compatibility.
Then, it would be a long-term work, and 64-bit coding will be before that.

Guan Xuetao

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/