All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Fabiano Rosas <farosas@linux.ibm.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	qemu-ppc@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [RFC PATCH v4 5/5] target/ppc: support single stepping with KVM HV
Date: Wed, 12 Jun 2019 16:31:16 +1000	[thread overview]
Message-ID: <c5e92072-eb8d-7af5-3eef-fac256f29c98@ozlabs.ru> (raw)
In-Reply-To: <eadc5e30-5094-9b76-7268-cfb633ac40bd@ozlabs.ru>

Are you reposting this any time soon?

In meanwhile I hit a problem when I cannot step over the "stdu" instruction.

I basically put this:
stdu    r1,-368(r1)

and "ni" in gdb does not stop on the next instruction which is quite
confusing. Ideas?


On 20/03/2019 12:42, Alexey Kardashevskiy wrote:
> 
> 
> On 20/03/2019 01:32, Fabiano Rosas wrote:
>> Alexey Kardashevskiy <aik@ozlabs.ru> writes:
>>
>>> Looks good to me, does not break what already works. However I cannot
>>> debug SLOF real mode and I am not sure why.
>>>
>>> (gdb) set endian big
>>>
>>> The target is assumed to be big endian
>>> (gdb) b *0x3f00
>>>
>>> Breakpoint 2 at 0x3f00
>>
>> I think I'm missing the point here. Why 0x3f00?
> 
> Because I am stupid and did not realize that 0x3f00 is a relative offset
> and 0x4000 is the correct address which works.
> 
> 
> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> 
> 
>>
>> (qemu) info roms
>> addr=0000000000000000 size=0x0e22b8 mem=ram name="...qemu/slof.bin"                               
>> addr=0000000000400000 size=0x17976d0 mem=ram name="...vmlinux"
>>
>>
>> $ objdump -d board-qemu/llfw/stage1.elf | grep "_start>"
>> 0000000000000100 <__start>:
>>      100:       48 00 3f 00     b       4000 <_start>
>> 0000000000004000 <_start>:
>>
>>
>> Thread 1 hit Breakpoint 3, _start () at startup.S:82
>> (gdb) p/x $pc
>> $1 = 0x4000
>> (gdb) si
>> (gdb) p/x $pc
>> $3 = 0x4004
>> (gdb) c
>> Thread 1 hit Breakpoint 4, early_c_entry (start_addr=49056, fdt_addr=49024) at stage2.c:202
>> (gdb) p/x $pc
>> $4 = 0x4d18
>>
> 

-- 
Alexey


  parent reply	other threads:[~2019-06-12  6:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 22:57 [Qemu-devel] [RFC PATCH v4 0/5] target/ppc: single step for KVM HV Fabiano Rosas
2019-02-28 22:57 ` [Qemu-devel] [RFC PATCH v4 1/5] target/ppc: Move exception vector offset computation into a function Fabiano Rosas
2019-03-04  5:36   ` David Gibson
2019-02-28 22:57 ` [Qemu-devel] [RFC PATCH v4 2/5] kvm-all: Introduce kvm_set_singlestep Fabiano Rosas
2019-03-04  5:50   ` David Gibson
2019-03-04 12:58     ` Fabiano Rosas
2019-03-08 19:09     ` Fabiano Rosas
2019-02-28 22:57 ` [Qemu-devel] [RFC PATCH v4 3/5] target/ppc: Move handling of hardware breakpoints to a separate function Fabiano Rosas
2019-03-04  5:51   ` David Gibson
2019-02-28 22:57 ` [Qemu-devel] [RFC PATCH v4 4/5] target/ppc: Refactor kvm_handle_debug Fabiano Rosas
2019-03-04  5:56   ` David Gibson
2019-02-28 22:57 ` [Qemu-devel] [RFC PATCH v4 5/5] target/ppc: support single stepping with KVM HV Fabiano Rosas
     [not found]   ` <b8a30b89-8c19-821e-e3a3-f1b71a088d9d@ozlabs.ru>
     [not found]     ` <87ef73rl39.fsf@linux.ibm.com>
     [not found]       ` <eadc5e30-5094-9b76-7268-cfb633ac40bd@ozlabs.ru>
2019-06-12  6:31         ` Alexey Kardashevskiy [this message]
2019-06-12 13:34           ` Fabiano Rosas
2019-06-12 23:27             ` Alexey Kardashevskiy
2019-06-13  2:01               ` Fabiano Rosas
2019-06-13  6:03                 ` Alexey Kardashevskiy

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=c5e92072-eb8d-7af5-3eef-fac256f29c98@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=farosas@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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.