qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Introduce foreach_cpu shorthand
Date: Thu, 05 Jun 2008 09:11:47 +0200	[thread overview]
Message-ID: <484791B3.9010505@web.de> (raw)
In-Reply-To: <200806050226.42967.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

Paul Brook wrote:
> [foreach_cpu]
>>> I tend to dislike such macros...
>> Why?
> 
> I agree with Fabrice in this case. Iterating over all cpus isn't a 
> particularly onerous task to start with. Using bizarre macros means that the 
> code no longer looks like normal C.

OK, got it. Looks like tastes are different here.

> 
>> My debugger SMP fix already comes with 5 more use cases.
> 
> I'm unconvinced by SMP debugger support. FSF gdb isn't currently capable of 
> handling SMP targets, so whatever you're doing is likely to be an ugly hack.

Well, it makes things useable on SMP hosts. Please suggest alternatives
if you think that this is the wrong approach, but leaving this unfixed
would be a mistake IMO.

Also note that gdb used for this case is in no way different from gdb
used with the kgdb stub. In both cases, the debugger (silently) expects
global scope of breakpoints. And that is what my patch ensures + it
enables focus switching for the gdbstub. Again, I'm open for alternative
approaches to achieve comparable usability. I can only repeat that
debugging SMP guest _depends_ on such changes.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

      reply	other threads:[~2008-06-05  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 19:56 [Qemu-devel] [PATCH] Introduce foreach_cpu shorthand Jan Kiszka
2008-06-03 20:18 ` Anthony Liguori
2008-06-04 12:39 ` Fabrice Bellard
2008-06-04 18:21   ` [Qemu-devel] " Jan Kiszka
2008-06-04 22:01     ` Thiemo Seufer
2008-06-04 22:29       ` Jan Kiszka
2008-06-05  1:26     ` Paul Brook
2008-06-05  7:11       ` Jan Kiszka [this message]

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=484791B3.9010505@web.de \
    --to=jan.kiszka@web.de \
    --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).