On 06/04/2015 08:32 AM, Chen Gang wrote:
On 06/03/2015 11:47 PM, Richard Henderson wrote:
That said, I don't have the system architecture manual
handy to check the full details.
Fortunately, Chris knows more about it, and provide more valuable
details for it.
And welcome any members to
On 07/09/2015 03:24 AM, Chris Metcalf wrote:
On 06/04/2015 08:32 AM, Chen Gang wrote:
On 06/03/2015 11:47 PM, Richard Henderson wrote:
That said, I don't have the system architecture manual
handy to check the full details.
Fortunately, Chris knows more about it, and provide more valuable
On 07/07/2015 08:19 AM, Chris Metcalf wrote:
I will be posting more hardware documents on Wednesday when I'm back in the
office.
That is good news! Thanks.
And at present, I am just analyzing the issue about the vi of busybox
with the static glibc (displaying and modifying contents through
On 07/07/2015 08:19 AM, Chris Metcalf wrote:
I will be posting more hardware documents on Wednesday when I'm back in the
office.
That is good news! Thanks.
And at present, I am just analyzing the issue about the vi of busybox
with the static glibc (displaying and modifying contents through
I will be posting more hardware documents on Wednesday when I'm back in the
office.
On Jun 4, 2015, at 5:33 AM, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 11:47 PM, Richard Henderson wrote:
On 06/03/2015 05:34 AM, Peter Maydell wrote:
You must do something. You can't
On 06/03/2015 11:20 PM, Chris Metcalf wrote:
On 06/03/2015 11:19 AM, Peter Maydell wrote:
On 3 June 2015 at 16:10, Chris Metcalf cmetc...@ezchip.com wrote:
On 06/03/2015 08:47 AM, Chen Gang wrote:
On 06/03/2015 08:34 PM, Peter Maydell wrote:
You must do something. You can't allow guest code
On 4 June 2015 at 13:25, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 11:20 PM, Chris Metcalf wrote:
On 06/03/2015 11:19 AM, Peter Maydell wrote:
On 3 June 2015 at 16:10, Chris Metcalf cmetc...@ezchip.com wrote:
On 06/03/2015 08:47 AM, Chen Gang wrote:
On 06/03/2015 08:34 PM,
On 06/03/2015 11:47 PM, Richard Henderson wrote:
On 06/03/2015 05:34 AM, Peter Maydell wrote:
You must do something. You can't allow guest code (even
broken guest code) to make QEMU assert. You need to find
out what the hardware does here, and do that.
These are I/O registers for IPC.
I
On 06/04/2015 08:29 PM, Peter Maydell wrote:
On 4 June 2015 at 13:25, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 11:20 PM, Chris Metcalf wrote:
On 06/03/2015 11:19 AM, Peter Maydell wrote:
On 3 June 2015 at 16:10, Chris Metcalf cmetc...@ezchip.com wrote:
On 06/03/2015 08:47
On 3 June 2015 at 13:30, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 01:40 AM, Peter Maydell wrote:
On 30 May 2015 at 22:10, Chen Gang xili_gchen_5...@hotmail.com wrote:
+#ifdef TARGET_TILEGX
+
+static uint64_t get_regval(CPUTLGState *env, uint8_t reg)
+{
+if (likely(reg
On 06/03/2015 08:34 PM, Peter Maydell wrote:
On 3 June 2015 at 13:30, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 01:40 AM, Peter Maydell wrote:
On 30 May 2015 at 22:10, Chen Gang xili_gchen_5...@hotmail.com wrote:
+#ifdef TARGET_TILEGX
+
+static uint64_t
On 06/03/2015 01:40 AM, Peter Maydell wrote:
On 30 May 2015 at 22:10, Chen Gang xili_gchen_5...@hotmail.com wrote:
+#ifdef TARGET_TILEGX
+
+static uint64_t get_regval(CPUTLGState *env, uint8_t reg)
+{
+if (likely(reg TILEGX_R_COUNT)) {
+return env-regs[reg];
+} else if
On 06/03/2015 11:19 AM, Peter Maydell wrote:
On 3 June 2015 at 16:10, Chris Metcalf cmetc...@ezchip.com wrote:
On 06/03/2015 08:47 AM, Chen Gang wrote:
On 06/03/2015 08:34 PM, Peter Maydell wrote:
You must do something. You can't allow guest code (even
broken guest code) to make QEMU assert.
On 06/03/2015 08:47 AM, Chen Gang wrote:
On 06/03/2015 08:34 PM, Peter Maydell wrote:
On 3 June 2015 at 13:30, Chen Gang xili_gchen_5...@hotmail.com wrote:
On 06/03/2015 01:40 AM, Peter Maydell wrote:
On 30 May 2015 at 22:10, Chen Gang xili_gchen_5...@hotmail.com wrote:
+#ifdef TARGET_TILEGX
On 06/03/2015 05:34 AM, Peter Maydell wrote:
You must do something. You can't allow guest code (even
broken guest code) to make QEMU assert. You need to find
out what the hardware does here, and do that.
These are I/O registers for IPC.
I believe that the best thing to do is assume protection
On 3 June 2015 at 16:10, Chris Metcalf cmetc...@ezchip.com wrote:
On 06/03/2015 08:47 AM, Chen Gang wrote:
On 06/03/2015 08:34 PM, Peter Maydell wrote:
You must do something. You can't allow guest code (even
broken guest code) to make QEMU assert. You need to find
out what the hardware does
On 30 May 2015 at 22:10, Chen Gang xili_gchen_5...@hotmail.com wrote:
Add main working flow feature, system call processing feature, and elf64
tilegx binary loading feature, based on Linux kernel tilegx 64-bit
implementation.
Signed-off-by: Chen Gang gang.chen.5...@gmail.com
---
Add main working flow feature, system call processing feature, and elf64
tilegx binary loading feature, based on Linux kernel tilegx 64-bit
implementation.
Signed-off-by: Chen Gang gang.chen.5...@gmail.com
---
include/elf.h | 2 +
linux-user/elfload.c | 23 +
18 matches
Mail list logo
