[Qemu-devel] [Bug 1344320] Re: qemu-aarch64 cannot execute glibc

[Peter Maydell]

To summarise the situation here:

 * in ARMv8 the Generic Timers are mandatory at the architectural/hardware level
 * however the kernel folks do not want to guarantee that they are always 
exposed to userspace (they want the flexibility in future to disable the 
userspace access for possible errata workarounds on future boards/CPUs)
 * the glibc change has been reverted upstream: 
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=33ef2f0c763b51e1df7896d7d39d585824558c75

So I'm closing this bug because QEMU's behaviour currently is fine. If
the kernel folk define a hwcap for timer access we can consider both
exposing the generic timers and setting the hwcap then. (Alternatively
if we ever get round to defining a VDSO for QEMU linux-user mode we
might want the timer access for that, as the kernel does.)


** Changed in: qemu
       Status: New => Invalid

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1344320

Title:
  qemu-aarch64 cannot execute glibc

Status in QEMU:
  Invalid

Bug description:
  $ aarch64-linux-user/qemu-aarch64 -version
  qemu-aarch64 version 2.0.92, Copyright (c) 2003-2008 Fabrice Bellard
  $ aarch64-linux-user/qemu-aarch64 -d in_asm 
/daten/build/build-root/home/abuild/rpmbuild/BUILD/glibc-2.19.90/cc-base/elf/ld-linux-aarch64.so.1
 
  host mmap_min_addr=0x10000
  guest_base  0x0
  start            end              size             prot
  0000004000000000-000000400001e000 000000000001e000 r-x
  000000400001e000-000000400002e000 0000000000010000 ---
  000000400002e000-0000004000031000 0000000000003000 rw-
  0000004000031000-0000004000032000 0000000000001000 ---
  0000004000032000-0000004000832000 0000000000800000 rw-
  start_brk   0x0000000000000000
  end_code    0x000000400001dbe0
  start_code  0x0000004000000000
  start_data  0x000000400002eba8
  end_data    0x0000004000030008
  start_stack 0x0000004000830a10
  brk         0x0000004000030170
  entry       0x00000040000012c0
  ----------------
  IN: 
  0x00000040000012c0:  910003e0      mov x0, sp
  0x00000040000012c4:  94000d4f      bl #+0x353c (addr 0x7fffb5bdad68)

  ----------------
  IN: _dl_start
  0x0000004000004800:  d11243ff      sub sp, sp, #0x490 (1168)
  0x0000004000004804:  a9ba7bfd      stp x29, x30, [sp, #-96]!
  0x0000004000004808:  910003fd      mov x29, sp
  0x000000400000480c:  a9046bf9      stp x25, x26, [sp, #64]
  0x0000004000004810:  a90153f3      stp x19, x20, [sp, #16]
  0x0000004000004814:  a9025bf5      stp x21, x22, [sp, #32]
  0x0000004000004818:  a90363f7      stp x23, x24, [sp, #48]
  0x000000400000481c:  a90573fb      stp x27, x28, [sp, #80]
  0x0000004000004820:  aa0003fa      mov x26, x0
  0x0000004000004824:  d5033fdf      isb
  0x0000004000004828:  d53be040      mrs x0, (unknown)

  qemu: uncaught target signal 4 (Illegal instruction) - core dumped
  Illegal instruction
  $ objdump -d 
/daten/build/build-root/home/abuild/rpmbuild/BUILD/glibc-2.19.90/cc-base/elf/ld-linux-aarch64.so.1
 | grep ' 4828:'
      4828:       d53be040        mrs     x0, cntvct_el0

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1344320/+subscriptions