All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: kvm@vger.kernel.org
Cc: pfeiner@google.com, pbonzini@redhat.com, rkrcmar@redhat.com
Subject: [kvm-unit-tests PATCH 0/8] arm: fix building by adding a feature
Date: Tue, 19 Apr 2016 16:28:02 +0200	[thread overview]
Message-ID: <1461076090-24308-1-git-send-email-drjones@redhat.com> (raw)

The main motivator of this series is to get the arm build fixed.
522667917 "lib: backtrace printing" added a common backtrace()
function, but we missed that arm's __builtin_return_address only
accepts the input 0, and thus the function, which calls it with
all values 0 to 20, can't compile on arm. To fix backtrace() for
arm, the easiest thing to do is to override it with a backtrace
that works. So this series makes some cleanups to stack tracing
support and adds the support for ARM.


Andrew Jones (8):
  x86: change exit to abort again
  x86: trivial: there's no dump_stack.o
  pretty_print_stacks: keep the 'STACK:' line
  pretty_print_stacks: use elf file for the kernel
  pretty_print_stacks: addr2line may need a cross prefix
  stack: share api prototypes
  stack: copy common asm/stack.h bits to all arches
  arm: stack: add dump_stack support

 arm/Makefile.arm               |  4 ++++
 configure                      |  2 ++
 lib/arm/asm/stack.h            | 11 +++++++++++
 lib/arm/processor.c            |  1 +
 lib/arm/stack.c                | 41 +++++++++++++++++++++++++++++++++++++++++
 lib/arm64/asm/stack.h          |  8 ++++++++
 lib/powerpc/asm/stack.h        |  8 ++++++++
 lib/ppc64/asm/stack.h          |  8 ++++++++
 lib/stack.h                    |  9 +++++----
 lib/x86/asm/stack.h            |  3 ---
 lib/x86/desc.c                 |  2 +-
 scripts/pretty_print_stacks.py | 14 +++++++++++---
 x86/Makefile.common            |  2 +-
 13 files changed, 101 insertions(+), 12 deletions(-)
 create mode 100644 lib/arm/stack.c

-- 
2.4.11


             reply	other threads:[~2016-04-19 14:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 14:28 Andrew Jones [this message]
2016-04-19 14:28 ` [kvm-unit-tests PATCH 1/8] x86: change exit to abort again Andrew Jones
2016-04-19 15:30   ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 2/8] x86: trivial: there's no dump_stack.o Andrew Jones
2016-04-19 15:31   ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 3/8] pretty_print_stacks: keep the 'STACK:' line Andrew Jones
2016-04-19 15:31   ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 4/8] pretty_print_stacks: use elf file for the kernel Andrew Jones
2016-04-19 14:53   ` Andrew Jones
2016-04-19 15:41     ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 5/8] pretty_print_stacks: addr2line may need a cross prefix Andrew Jones
2016-04-19 15:33   ` Peter Feiner
2016-04-19 15:45     ` Andrew Jones
2016-04-19 14:28 ` [kvm-unit-tests PATCH 6/8] stack: share api prototypes Andrew Jones
2016-04-19 15:37   ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 7/8] stack: copy common asm/stack.h bits to all arches Andrew Jones
2016-04-19 15:38   ` Peter Feiner
2016-04-19 14:28 ` [kvm-unit-tests PATCH 8/8] arm: stack: add dump_stack support Andrew Jones
2016-04-19 15:41   ` Peter Feiner
2016-04-19 15:55     ` Andrew Jones

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=1461076090-24308-1-git-send-email-drjones@redhat.com \
    --to=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pfeiner@google.com \
    --cc=rkrcmar@redhat.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.