All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] gdbstub broken in master
Date: Tue, 09 Jul 2013 23:47:19 +0200	[thread overview]
Message-ID: <51DC84E7.6090609@suse.de> (raw)
In-Reply-To: <CAMo8BfJuJDZE02yhDHKVhyKpHhXOxe5MR9KoABCWTeY+U2y0BA@mail.gmail.com>

Hi Max,

Am 09.07.2013 01:37, schrieb Max Filippov:
> commit c52a6b67c1d7c6fc9fb2e3ba988d7b978e1487d3
> Author: Andreas Färber <afaerber@suse.de>
> Date:   Fri May 17 17:49:10 2013 +0200
> 
>     gdbstub: Simplify find_cpu()
> 
>     Use qemu_get_cpu() and CPUState::env_ptr.
> 
>     Reviewed-by: Richard Henderson <rth@twiddle.net>
>     Signed-off-by: Andreas Färber <afaerber@suse.de>
> 
> breaks single-stepping in gdb. This commit replaces
> 
>         if (cpu_index(cpu) == thread_id) {
> 
> with qemu_get_cpu(thread_id) call, which does the following:
> 
>         if (cpu->cpu_index == index) {
> 
> while cpu_index(cpu) used to return cpu->cpu_index + 1;

Ouch! Thanks for catching this, not sure how I managed to mix them up.

I've reverted this on qom-cpu (rebasing the first_cpu/next_cpu patch)
and dropped a queued patch replacing two find_cpu()s with that
qemu_get_cpu().
https://github.com/afaerber/qemu-cpu/commits/qom-cpu

The qom-cpu-11 branch has been updated to convert c_cpu, g_cpu and
find_cpu() to CPUState all in one go rather than replacing and dropping
the latter and doing the two fields separately. Can you give it a test?

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-07-09 21:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 23:37 [Qemu-devel] gdbstub broken in master Max Filippov
2013-07-09 21:47 ` Andreas Färber [this message]
2013-07-11  1:13   ` Max Filippov

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=51DC84E7.6090609@suse.de \
    --to=afaerber@suse.de \
    --cc=jcmvbkbc@gmail.com \
    --cc=qemu-devel@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.