From: Riku Voipio <riku.voipio@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Guan Xuetao" <gxt@mprc.pku.edu.cn>, 管雪涛 <gxt@pku.edu.cn>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Patch Tracking" <patches@linaro.org>
Subject: Re: [Qemu-devel] 回复： Re: 回复： Re: [PATCH] linux-user: sync syscall numbers upto 3.13
Date: Wed, 15 Jan 2014 10:09:48 +0200 [thread overview]
Message-ID: <CAAqcGHmsOBMjwNZXGZE5Sg0JqSRFvUB7wZYZBsLBSb3XnpDSJg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-VhvegPOjEhQh5xSvN0rtC_mHK2fzW_H3+4zs72ehs=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On 14 January 2014 12:50, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 14 January 2014 01:33, 管雪涛 <gxt@pku.edu.cn> wrote:
> > I'm sorry, but what's exactly your meaning?
> > Change linux-user/unicore32/syscall_nr.h to be the same as linux kernel.
>
> This. We should support the same set of binaries you can
> run on the upstream kernel.
>
I agree in principle, but qemu should also support running the binaries
that people actually use. So if old unicore32 abi is widely used, we should
support that also.
Guam, the new ABI has been in mainline linux for quite a long time - is
there even a plan to move to the new abi in unicore community?
Riku
[-- Attachment #2: Type: text/html, Size: 1119 bytes --]
prev parent reply other threads:[~2014-01-15 8:09 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 ` [Qemu-devel] 回复： " 管雪涛
2014-01-13 15:21 ` Peter Maydell
2014-01-14 1:33 ` [Qemu-devel] 回复： " 管雪涛
2014-01-14 10:50 ` Peter Maydell
2014-01-15 8:09 ` Riku Voipio [this message]
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=CAAqcGHmsOBMjwNZXGZE5Sg0JqSRFvUB7wZYZBsLBSb3XnpDSJg@mail.gmail.com \
--to=riku.voipio@linaro.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).