qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Laurent Vivier <Laurent@Vivier.EU>
Cc: aliguori@us.ibm.com, riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PING 0.14] Missing patches (mostly fixes)
Date: Wed, 9 Feb 2011 12:25:32 +0200	[thread overview]
Message-ID: <20110209102532.GA29059@afflict.kos.to> (raw)
In-Reply-To: <2254887.338399.1297243238443.JavaMail.servlet@pustefix155.kundenserver.de>

> >Actually that patch is not ok. The issues you fix on m68k appear
> >on arm/eabi after applying your patch. bswap part appears ok, but
> >the padding is needed atleast on arm.
 
> How do you test this patch ? Do you use native gdb on ARM ? Because, for m68k, cross-compiled gdb does not work (it cannot have sizeof(prstatus_t) for m68k).

I tried both native and cross-gdb, version 7.2. Both fail with your patch applied
and work fine without it.

Before your patch, objdump (CodeSourcery cs2009q3 cross) output looks like:

-snip-
Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 note0         000001bc  00000000  00000000  000000d4  2**0
                  CONTENTS, READONLY
  1 .reg/23968    00000048  00000000  00000000  00000130  2**2
                  CONTENTS
  2 .reg          00000048  00000000  00000000  00000130  2**2
                  CONTENTS
  3 .auxv         00000070  00000000  00000000  00000220  2**2
                  CONTENTS
  4 load1         00000000  00008000  00000000  00001000  2**12
                  ALLOC, READONLY, CODE
-snip-

after:

-snip-
Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 note0         000001bc  00000000  00000000  000000d4  2**0
                  CONTENTS, READONLY
  1 .auxv         00000070  00000000  00000000  00000220  2**2
                  CONTENTS
  2 load1         00000000  00008000  00000000  00001000  2**12
                  ALLOC, READONLY, CODE
                  CONTENTS, ALLOC, LOAD
-snip-

  parent reply	other threads:[~2011-02-09 10:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  9:20 [Qemu-devel] Re: [PING 0.14] Missing patches (mostly fixes) Laurent Vivier
2011-02-09  9:52 ` Peter Maydell
2011-02-09 10:25 ` Riku Voipio [this message]
2011-02-10 23:07   ` [Qemu-devel] [PATCH 0/2] correct core dump format Laurent Vivier
2011-02-10 23:07   ` [Qemu-devel] [PATCH 1/2] Define target alignment size Laurent Vivier
2011-02-10 23:07   ` [Qemu-devel] [PATCH 2/2] linux-user: correct core dump format Laurent Vivier
  -- strict thread matches above, loose matches on Subject: below --
2011-02-09 10:14 [Qemu-devel] Re: [PING 0.14] Missing patches (mostly fixes) Laurent Vivier
2011-02-05 21:49 Laurent Vivier
2011-02-09  7:03 ` Riku Voipio
2011-02-03 10:16 Laurent Vivier
2011-02-05 19:40 ` riku voipio
2011-02-07 13:09   ` Anthony Liguori
2011-01-27  8:29 [Qemu-devel] [0.14] Queue of 0.14 patches/pull? Paolo Bonzini
2011-02-02 19:28 ` [Qemu-devel] [PING 0.14] Missing patches (mostly fixes) Stefan Weil
2011-02-02 21:25   ` [Qemu-devel] " Michael S. Tsirkin
2011-02-03  7:00   ` Riku Voipio

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=20110209102532.GA29059@afflict.kos.to \
    --to=riku.voipio@iki.fi \
    --cc=Laurent@Vivier.EU \
    --cc=aliguori@us.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).