qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: 管雪涛 <gxt@pku.edu.cn>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@linaro.org>,
	Guan Xuetao <gxt@mprc.pku.edu.cn>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Patch Tracking <patches@linaro.org>
Subject: [Qemu-devel] 回复： Re:  [PATCH] linux-user: sync syscall numbers upto 3.13
Date: Mon, 13 Jan 2014 23:14:11 +0800 (CST)	[thread overview]
Message-ID: <1803379872.20279.1389626051959.JavaMail.root@bj-mail03.pku.edu.cn> (raw)
In-Reply-To: <CAFEAcA8fdfCh2La-LjM5-O1o697tHoqoaTTsRMUd-cpw28tL6w@mail.gmail.com>

The syscall numbers in unicore32 are correct because we have two ABIs for 32 bits.
In qemu, it's old ABI, while in kernel, it's new ABI.
However, for now, old ABI is widely used for unicore32's applications.

Thanks and Regards,

Xuetao Guan

----- Peter Maydell <peter.maydell@linaro.org> 写道：
> On 13 January 2014 12:33,  <riku.voipio@linaro.org> wrote:
> > From: Riku Voipio <riku.voipio@linaro.org>
> >
> > All others updated except unicore, which doesn't look right to
> > begin with.
> 
> Yes, I've noticed before that the Unicore syscall numbers are
> just completely wrong. Guan, would you like to submit a patch
> to fix them or should we just rip out the linux-user support
> for unicore completely? There's no point carrying something
> around that won't be able to do even basic syscalls...
> 
> thanks
> -- PMM

  reply	other threads:[~2014-01-13 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 12:33 [Qemu-devel] [PATCH] linux-user: sync syscall numbers upto 3.13 riku.voipio
2014-01-13 13:18 ` Peter Maydell
2014-01-13 15:14   ` 管雪涛 [this message]
2014-01-13 15:21     ` [Qemu-devel] 回复： " Peter Maydell
2014-01-14  1:33       ` [Qemu-devel] 回复： " 管雪涛
2014-01-14 10:50         ` Peter Maydell
2014-01-15  8:09           ` Riku Voipio

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=1803379872.20279.1389626051959.JavaMail.root@bj-mail03.pku.edu.cn \
    --to=gxt@pku.edu.cn \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@linaro.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).