All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xuetao Guan" <gxt@mprc.pku.edu.cn>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: MPRC <zhangheng@mprc.pku.edu.cn>,
	peter.maydell@linaro.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU
Date: Mon, 26 Sep 2016 13:45:20 +0800 (CST)	[thread overview]
Message-ID: <63934.117.114.135.40.1474868720.squirrel@mprc.pku.edu.cn> (raw)
In-Reply-To: <20160923074649.GA4827@kos.to>

> 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
>
OK, I see.
I'd send kernel-patches merge request to linus, but the patches hadn't be
merged.
I'll work on it. Hopefully it'll be done before mid Oct.

Thanks Riku and Peter

Guan Xuetao

  reply	other threads:[~2016-09-26  5:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 15:09 [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU MPRC
2016-09-23  7:46 ` Riku Voipio
2016-09-26  5:45   ` Xuetao Guan [this message]
2016-09-28 16:18     ` Riku Voipio
2016-09-29  8:04       ` Xuetao Guan
  -- strict thread matches above, loose matches on Subject: below --
2016-05-12 14:34 Peter Maydell
2016-05-12 17:19 ` Richard Henderson
2016-05-20 12:48 ` Riku Voipio
2016-06-14 12:14   ` Peter Maydell
2016-06-14 13:43     ` Xuetao Guan
2016-09-11 15:08       ` Peter Maydell
2016-09-12  0:51         ` Xuetao Guan

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=63934.117.114.135.40.1474868720.squirrel@mprc.pku.edu.cn \
    --to=gxt@mprc.pku.edu.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=zhangheng@mprc.pku.edu.cn \
    /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.