qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <1900779@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1900779] Re: xp /16i on arm mixes DWords
Date: Thu, 22 Oct 2020 13:38:32 -0000	[thread overview]
Message-ID: <160337391257.31600.16105620749858959285.malone@gac.canonical.com> (raw)
In-Reply-To: 160324353545.18570.15111142462284405315.malonedeb@chaenomeles.canonical.com

Thanks for the bug report; I've just posted a patch which should fix it:
https://patchew.org/QEMU/20201022132445.25039-1-peter.maydell@linaro.org/

** Changed in: qemu
       Status: Confirmed => In Progress

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

Title:
  xp /16i on arm mixes DWords

Status in QEMU:
  In Progress

Bug description:
  I was working with qemuand wanted to understag ATAG structure.
  In Monitor mode I used xp /16i 0x100 and I got really confused.
  with xp /16i 0x100:
  At address 0x120 the DWords are 0x00000000, 0x00000004, 0x54410009, 0x74736574
  with xp /16x 0x100:
  At address 0x120 the DWords are 0x54410001, 0x00000001, 0x00000001, 0x00000000

  from my Terminal:

  (qemu) xp /16x 0x100
  0000000000000100: 0x00000005 0x54410001 0x00000001 0x00001000
  0000000000000110: 0x00000000 0x00000004 0x54410002 0x3c000000
  0000000000000120: 0x00000000 0x00000004 0x54410009 0x74736574
  0000000000000130: 0x00000000 0x00000000 0x00000000 0x00000000
  (qemu) xp /16i 0x100
  0x00000100:  00000005  andeq    r0, r0, r5
  0x00000104:  54410001  strbpl   r0, [r1], #-1
  0x00000108:  00000001  andeq    r0, r0, r1
  0x0000010c:  00001000  andeq    r1, r0, r0
  0x00000110:  00000000  andeq    r0, r0, r0
  0x00000114:  00000004  andeq    r0, r0, r4
  0x00000118:  54410002  strbpl   r0, [r1], #-2
  0x0000011c:  3c000000  .byte    0x00, 0x00, 0x00, 0x3c
  0x00000120:  54410001  strbpl   r0, [r1], #-1
  0x00000124:  00000001  andeq    r0, r0, r1
  0x00000128:  00001000  andeq    r1, r0, r0
  0x0000012c:  00000000  andeq    r0, r0, r0
  0x00000130:  00000004  andeq    r0, r0, r4
  0x00000134:  54410002  strbpl   r0, [r1], #-2
  0x00000138:  3c000000  .byte    0x00, 0x00, 0x00, 0x3c
  0x0000013c:  00000000  andeq    r0, r0, r0
  (increasing length only results in more 00000000  andeq    r0, r0, r0 Lines)

  Version:
  4.2.1Debian 1:4.2-3ubuntu6.6
  Commandline:
  qemu-system-arm -machine raspi2 --nographic -S -s -kernel ./vmlinuz --append "test"
  ./vmlinuz is a x64 linux kernel. I didn't care about architecture because i just wanted to see ATAG structure.
  I also tried
  qemu-system-arm -machine raspi2 --nographic -S -s -kernel ./overview.pdf --append "test"
  same result.

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


  parent reply	other threads:[~2020-10-22 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21  1:25 [Bug 1900779] [NEW] xp /16i on arm mixes DWords Chaoscode
2020-10-21  2:05 ` [Bug 1900779] " Chaoscode
2020-10-22 12:14 ` Peter Maydell
2020-10-22 13:38 ` Peter Maydell [this message]
2020-11-04 22:23 ` John Snow
2020-11-04 22:27 ` John Snow
2020-12-10  8:49 ` Thomas Huth

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=160337391257.31600.16105620749858959285.malone@gac.canonical.com \
    --to=1900779@bugs.launchpad.net \
    --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).