From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-trivial <qemu-trivial@nongnu.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH] gdbstub: Set current CPU on interruptions
Date: Mon, 27 Jul 2015 22:46:34 +0300 [thread overview]
Message-ID: <55B68A9A.9000707@msgid.tls.msk.ru> (raw)
In-Reply-To: <55B26D4F.3040108@siemens.com>
24.07.2015 19:52, Jan Kiszka wrote:
> gdb expects that the thread ID for c and g-class operations is set to
> the CPU we provide when reporting VM stop conditions. If the stub is
> still tuned to a different CPU, the wrong information is delivered to
> the gdb frontend.
Applied to -trivial, thanks!
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-trivial <qemu-trivial@nongnu.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] gdbstub: Set current CPU on interruptions
Date: Mon, 27 Jul 2015 22:46:34 +0300 [thread overview]
Message-ID: <55B68A9A.9000707@msgid.tls.msk.ru> (raw)
In-Reply-To: <55B26D4F.3040108@siemens.com>
24.07.2015 19:52, Jan Kiszka wrote:
> gdb expects that the thread ID for c and g-class operations is set to
> the CPU we provide when reporting VM stop conditions. If the stub is
> still tuned to a different CPU, the wrong information is delivered to
> the gdb frontend.
Applied to -trivial, thanks!
/mjt
next prev parent reply other threads:[~2015-07-27 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 16:52 [Qemu-trivial] [PATCH] gdbstub: Set current CPU on interruptions Jan Kiszka
2015-07-24 16:52 ` [Qemu-devel] " Jan Kiszka
2015-07-27 19:46 ` Michael Tokarev [this message]
2015-07-27 19:46 ` Michael Tokarev
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=55B68A9A.9000707@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.