From: Arnd Bergmann <arnd@arndb.de>
To: Guan Xuetao <guanxuetao@mprc.pku.edu.cn>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Unicore architecture patch review, part 2
Date: Wed, 8 Dec 2010 13:53:44 +0100 [thread overview]
Message-ID: <201012081353.44927.arnd@arndb.de> (raw)
In-Reply-To: <011401cb96c0$b7dca8d0$2795fa70$@mprc.pku.edu.cn>
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?
> > Hmm, when the architecture was being defined, why didn't you ask for a
> > cycle counter? It really improves the delay code a lot.
> No software readable cycle counter in UniCore32.
>
> > If you have a good time base by now, you should use it. Is the OST_OSCR
> > something you could use here?
> OST_OSCR is much coarse in here, which is 14.318M Hz.
Ok, I see.
Arnd
next prev parent reply other threads:[~2010-12-08 12:53 UTC|newest]
Thread overview: 9+ 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 [this message]
2010-12-09 3:37 ` Guan Xuetao
2010-12-09 3:37 ` Guan Xuetao
2010-12-10 13:10 ` Arnd Bergmann
2010-12-13 7:14 ` Guan Xuetao
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=201012081353.44927.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=guanxuetao@mprc.pku.edu.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.