From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YM2IN-0001Bd-R0 for qemu-devel@nongnu.org; Thu, 12 Feb 2015 17:31:40 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YM2IK-0006hs-ID for qemu-devel@nongnu.org; Thu, 12 Feb 2015 17:31:39 -0500 Received: from mail-db3on0097.outbound.protection.outlook.com ([157.55.234.97]:14368 helo=emea01-db3-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YM2IK-0006gz-9l for qemu-devel@nongnu.org; Thu, 12 Feb 2015 17:31:36 -0500 Message-ID: <54DD29BA.4040003@ezchip.com> Date: Thu, 12 Feb 2015 17:31:22 -0500 From: Chris Metcalf MIME-Version: 1.0 References: <54DBED38.4060005@sunrus.com.cn> <54DBEFD3.1070609@sunrus.com.cn> <54DBF2D2.3000802@ezchip.com> <54DC1EC7.9000808@sunrus.com.cn> In-Reply-To: <54DC1EC7.9000808@sunrus.com.cn> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] tile: Can load elf64 tilegx binary successfully for linux-user. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chen Gang S , riku.voipio@iki.fi, Peter Maydell Cc: "walt@tilera.com" , qemu-devel 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