All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, Guan Xuetao <gxt@mprc.pku.edu.cn>
Subject: Re: [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU
Date: Thu, 12 May 2016 07:19:46 -1000	[thread overview]
Message-ID: <589613c2-63ee-a999-dc40-870dbdfd7e51@twiddle.net> (raw)
In-Reply-To: <CAFEAcA8zz0AYcy60fknmxa3chTsEyq0OvhvHpnSRF-Utgvf2oA@mail.gmail.com>

On 05/12/2016 04:34 AM, Peter Maydell wrote:
> QEMU has something that claims to be linux-user support for
> the unicore32 guest CPU. However the syscall numbers in
> linux-user/unicore32 are nothing like those actually implemented
> in the upstream kernel (which uses asm-generic syscall numbers).
>
> We should either fix our unicore32 support to use the real
> syscall numbers, or just drop it; since nobody has touched
> linux-user/unicore32 since 2012, and there have been no
> commits to target-unicore32 that aren't generic "clean up
> all targets" type patches since 2012 or 2013, and nobody
> has ever complained that the syscall numbers are all broken,
> my initial inclination is to say we should just drop this.

No objections.


r~

  reply	other threads:[~2016-05-12 17:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 14:34 [Qemu-devel] proposal: drop linux-user unicore32 support from QEMU Peter Maydell
2016-05-12 17:19 ` Richard Henderson [this message]
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
2016-09-22 15:09 MPRC
2016-09-23  7:46 ` Riku Voipio
2016-09-26  5:45   ` Xuetao Guan
2016-09-28 16:18     ` Riku Voipio
2016-09-29  8:04       ` 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=589613c2-63ee-a999-dc40-870dbdfd7e51@twiddle.net \
    --to=rth@twiddle.net \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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.