All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@ezchip.com>
To: Chen Gang S <gang.chen@sunrus.com.cn>,
	riku.voipio@iki.fi, Peter Maydell <peter.maydell@linaro.org>
Cc: "walt@tilera.com" <walt@tilera.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user.
Date: Thu, 12 Feb 2015 17:31:22 -0500	[thread overview]
Message-ID: <54DD29BA.4040003@ezchip.com> (raw)
In-Reply-To: <54DC1EC7.9000808@sunrus.com.cn>

On 2/11/2015 10:32 PM, Chen Gang S wrote:
>>> + */
>>> +#define TARGET_NR_io_setup                      0
>>> +#define TARGET_NR_io_destroy                    1
>>> +#define TARGET_NR_io_submit                     2
>> [...]
>>
>> Isn't there a way to say "use the asm-generic syscalls"?  What does ARM64 do, for example?  They use the generic syscall list.
>>
>>> [...]
>>> +#define TARGET_NR_bpf                           280
>>> +#define TARGET_NR_execveat                      281
>>> +
> Do you mean we need to remove them?

No, I'm saying it would be good to be able to have a single shared header that listed all the asm-generic syscall numbers that could be shared by tile, arm64, etc.

>>> +/* current tilegx Linux kernel do not want to support the macros below */
>>> +
>> Probably better not to define them, then look at fixing anything that breaks as a result.  Again, ARM64 will be the same.
>>
> Do you mean we do not need to define the macros below?
>
>    #define TARGET_NR_open 1024
>    #define TARGET_NR_link 1025
>    #define TARGET_NR_unlink 1026

That's my suggestion, yes.

> And excuse me, my English is not quite well, I don't quite understand:
>
>    "fixing anything that breaks as a result".
>
> Could you provide more details? Thanks.

So if you undefine TARGET_NR_open, etc, hopefully qemu will build. If it does not build, you should probably find out why, and fix it. Perhaps you can use NR_openat as a replacement for NR_open, etc.

>> Tilera did some work on a qemu port only intended to be used with KVM for virtualization, so it probably doesn't do you much good.  If you're interested, I can send you the diffs.
>>
> Welcome the related diffs, I guess, it must be helpful. :-)

I uploaded it to:

   http://173.201.26.195/scm/qemu-kvm-0.13.0.get

Notice that this is against a much older version of qemu, though.

-- 
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com

  parent reply	other threads:[~2015-02-12 22:31 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 [this message]
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
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=54DD29BA.4040003@ezchip.com \
    --to=cmetcalf@ezchip.com \
    --cc=gang.chen@sunrus.com.cn \
    --cc=peter.maydell@linaro.org \
    --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 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.