From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38884)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnLCJ-0002uZ-BH
	for qemu-devel@nongnu.org; Fri, 23 Sep 2016 03:47:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnLCE-0001dz-E0
	for qemu-devel@nongnu.org; Fri, 23 Sep 2016 03:47:03 -0400
Received: from jessie.kos.to ([212.47.231.226]:59464 helo=pilvi.kos.to)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <voipio@kos.to>) id 1bnLCE-0001cU-7w
	for qemu-devel@nongnu.org; Fri, 23 Sep 2016 03:46:58 -0400
Date: Fri, 23 Sep 2016 07:46:49 +0000
From: Riku Voipio <riku.voipio@iki.fi>
Message-ID: <20160923074649.GA4827@kos.to>
References: <006C2BF7-5EF8-422A-A08C-4378D0E861F3@mprc.pku.edu.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006C2BF7-5EF8-422A-A08C-4378D0E861F3@mprc.pku.edu.cn>
Subject: Re: [Qemu-devel] proposal: drop linux-user unicore32 support from
 QEMU
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: MPRC <zhangheng@mprc.pku.edu.cn>
Cc: peter.maydell@linaro.org, Guan Xuetao <gxt@mprc.pku.edu.cn>, qemu-devel@nongnu.org

On Thu, Sep 22, 2016 at 11:09:55PM +0800, MPRC wrote:
> Hi, I'm fixing the syscall problem for linux-user/unicore32 in qemu.
> 
> I write a "hello world" program to test linux-user/unicore32 in qemu 2.7 with toolchain of uc4-1.0.5(you can download it through http://mprc.pku.edu.cn/~guanxuetao/linux/uc4-1.0.5-hard.tgz). And it's just OK.
> It goes well in the old version qemu that we using, also.
> 
> Can you discribe the bug more detailed? Or how do you find that the unicore32 don't use the real syscall numbers?
> How should test this? By Linux Test Project? It's not necessary to do all test in LTP.

The problem we see is that the system call numbers in qemus
unicore32/syscall_nr.h dont match what is linux mainline kernel. From the
toolchain linked, you seem to have kernel headers and syscall numbers 
based on a custom 2.6.32 fork. If one builds unicore32 binaries based on
Linux 4.4 kernel headers, they will not work qemu. OTOH the binary built
with the toolchain you linked, would not work with linux 4.4. This
disparity is what we'd like to get fixed.

Riku