From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Cc: borntraeger@de.ibm.com, qemu-devel@nongnu.org, palves@redhat.com,
alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH v7 2/2] gdbstub: Fix vCont behaviour
Date: Mon, 6 Feb 2017 11:00:43 +0100 [thread overview]
Message-ID: <63aaa3cc-6623-374d-8f8f-4e48fbbc21ce@redhat.com> (raw)
In-Reply-To: <1485540693-31723-3-git-send-email-imbrenda@linux.vnet.ibm.com>
On 27/01/2017 19:11, Claudio Imbrenda wrote:
> + /* mark valid CPUs with 1 */
> + CPU_FOREACH(cpu) {
> + newstates[cpu_index(cpu) - 1] = 1;
> + }
Sorry I didn't notice this before: CPU indices are zero-based in QEMU,
so you are probably overwriting newstates[-1]. I can adjust it myself,
but can you please double check?
Paolo
> +
> + /*
> + * res keeps track of what error we are returning, with -1 meaning
> + * that the command is unknown or unsupported, and thus returning
> + * an empty packet, while -22 returns an E22 packet due to
> + * invalid or incorrect parameters passed.
> + */
> + res = 0;
> + while (*p) {
> + if (*p++ != ';') {
> + res = -ENOTSUP;
> + goto out;
> + }
> +
> + cur_action = *p++;
> + if (cur_action == 'C' || cur_action == 'S') {
> + cur_action = tolower(cur_action);
> + res = qemu_strtoul(p + 1, &p, 16, &tmp);
> + if (res) {
> + goto out;
> + }
> + signal = gdb_signal_to_target(tmp);
> + } else if (cur_action != 'c' && cur_action != 's') {
> + /* unknown/invalid/unsupported command */
> + res = -ENOTSUP;
> + goto out;
> + }
> + /* thread specification. special values: (none), -1 = all; 0 = any */
> + if ((p[0] == ':' && p[1] == '-' && p[2] == '1') || (p[0] != ':')) {
> + if (*p == ':') {
> + p += 3;
> + }
> + for (idx = 0; idx < max_cpus; idx++) {
> + if (newstates[idx] == 1) {
> + newstates[idx] = cur_action;
> + }
> + }
> + } else if (*p == ':') {
> + p++;
> + res = qemu_strtoul(p, &p, 16, &tmp);
> + if (res) {
> + goto out;
> + }
> + idx = tmp;
> + /* 0 means any thread, so we pick the first valid CPU */
> + if (!idx) {
> + idx = cpu_index(first_cpu);
> + }
> +
> + /* invalid CPU specified */
> + if (!idx || idx > max_cpus || !newstates[idx - 1]) {
> + res = -EINVAL;
> + goto out;
> + }
> + /* only use if no previous match occourred */
> + if (newstates[idx - 1] == 1) {
> + newstates[idx - 1] = cur_action;
> + }
> + }
next prev parent reply other threads:[~2017-02-06 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 18:11 [Qemu-devel] [PATCH v7 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2017-01-27 18:11 ` [Qemu-devel] [PATCH v7 1/2] move vm_start to cpus.c Claudio Imbrenda
2017-02-06 9:53 ` Paolo Bonzini
2017-01-27 18:11 ` [Qemu-devel] [PATCH v7 2/2] gdbstub: Fix vCont behaviour Claudio Imbrenda
2017-02-06 10:00 ` Paolo Bonzini [this message]
2017-02-07 9:59 ` Claudio Imbrenda
2017-02-07 15:10 ` Paolo Bonzini
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=63aaa3cc-6623-374d-8f8f-4e48fbbc21ce@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=palves@redhat.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).