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

> > 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.

> 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.

This blocks some cleanup work in linux-user code. For example everyone has
moved over from epoll_wait to epoll_pwait. However, I can't remove the now
unneeded TARGET_NR_epoll_pwait, because nobody is keeping unicore32 syscall
list upto date.

I think we should temporarily disable the unicore32-linux-user target, and
re-enable it in be 2.8 softfreeze if the system calls get updated.

Riku

  reply	other threads:[~2016-09-28 16:18 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
2016-09-28 16:18     ` Riku Voipio [this message]
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=20160928161832.GA4904@kos.to \
    --to=riku.voipio@iki.fi \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --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.