From: "Guan Xuetao" <guanxuetao@mprc.pku.edu.cn>
To: 'Arnd Bergmann' <arnd@arndb.de>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: [PATCH] Unicore architecture patch review, part 2
Date: Thu, 9 Dec 2010 11:37:58 +0800 [thread overview]
Message-ID: <017801cb9752$79a48a50$6ced9ef0$@mprc.pku.edu.cn> (raw)
In-Reply-To: <201012081353.44927.arnd@arndb.de>
> -----Original Message-----
> From: linux-arch-owner@vger.kernel.org [mailto:linux-arch-
> owner@vger.kernel.org] On Behalf Of Arnd Bergmann
> Sent: Wednesday, December 08, 2010 8:54 PM
> To: Guan Xuetao
> Cc: linux-arch@vger.kernel.org; linux-kernel@vger.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
next prev parent reply other threads:[~2010-12-09 3:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 16:54 [PATCH] Unicore architecture patch review, part 2 Arnd Bergmann
2010-12-08 10:14 ` Guan Xuetao
2010-12-08 10:14 ` Guan Xuetao
2010-12-08 12:53 ` Arnd Bergmann
2010-12-09 3:37 ` Guan Xuetao [this message]
2010-12-10 13:10 ` Arnd Bergmann
2010-12-13 7:14 ` Guan Xuetao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='017801cb9752$79a48a50$6ced9ef0$@mprc.pku.edu.cn' \
--to=guanxuetao@mprc.pku.edu.cn \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).