From: Peter Maydell <peter.maydell@linaro.org>
To: Chen Gang S <gang.chen@sunrus.com.cn>
Cc: "walt@tilera.com" <walt@tilera.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user.
Date: Fri, 13 Feb 2015 05:43:19 +0000 [thread overview]
Message-ID: <CAFEAcA_wRfuH9sp-fKHQNdQrnLtwA7T47KUVbNKq5C_AbRkJpQ@mail.gmail.com> (raw)
In-Reply-To: <54DD8F2F.2090703@sunrus.com.cn>
On 13 February 2015 at 05:44, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
> Which issue of correctness will occur? I can not enum it.
If the Linux kernel does not implement these syscalls then
QEMU must not either. Attempting them should fail, same as
if you attempted them with the real kernel.
> - linux-user already bypasses target linux kernel, and libc for tilegx
> can not generate these calls (not defined for libc, either).
Just because libc doesn't try to do these things doesn't mean
QEMU should do the wrong thing for them.
> - For any informal using, linux-user can still operate NR_open and
> others, it is harmless.
But it is still wrong.
-- PMM
next prev parent reply other threads:[~2015-02-13 5:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 0:00 [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user Chen Gang S
2015-02-12 0:12 ` Chen Gang S
2015-02-12 0:24 ` Chris Metcalf
2015-02-12 3:32 ` Chen Gang S
2015-02-12 3:48 ` Chen Gang S
2015-02-12 22:32 ` Chris Metcalf
2015-02-13 4:03 ` Chen Gang S
2015-02-12 22:31 ` Chris Metcalf
2015-02-13 4:43 ` Chen Gang S
2015-02-13 4:56 ` Peter Maydell
2015-02-13 5:44 ` Chen Gang S
2015-02-13 5:43 ` Peter Maydell [this message]
2015-02-13 6:34 ` Chen Gang S
2015-02-12 0:49 ` Peter Maydell
2015-02-12 2:53 ` Chen Gang S
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=CAFEAcA_wRfuH9sp-fKHQNdQrnLtwA7T47KUVbNKq5C_AbRkJpQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=cmetcalf@ezchip.com \
--cc=gang.chen@sunrus.com.cn \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=walt@tilera.com \
/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).