From: Tom Tromey <tromey@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] remote-sim.c: Add support for multiple sim instances
Date: Thu, 08 Jul 2010 20:08:00 -0000 [thread overview]
Message-ID: <m38w5l68jt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100702153017.4381070b@mesquite.lan> (Kevin Buettner's message of "Fri, 2 Jul 2010 15:30:17 -0700")
>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:
Kevin> A very nice side effect of this patch is that it is now possible to
Kevin> have more than one runnable simulator instance.
Cool.
Kevin> It seems to me that, long term, the right way to do it is to create a
Kevin> new sim instance for each invocation of "target sim". That, however,
Kevin> is not what I did.
[...]
Kevin> But, back to the "right way" for a moment. It seems to me that,
Kevin> ideally, we'd want to be able to have one inferior connected to a
Kevin> remote target, another to a simulator, another to a different remote
Kevin> target, yet another to a sim using a different architecture variant,
Kevin> etc. In order for that to happen, the target vector will need to
Kevin> become a per-inferior data structure.
Yeah, this has come up a few times now. Somewhere, fairly recently,
Pedro mentioned his preferred approach to this.
Kevin> Comments? Okay to commit?
This isn't an area I am comfortable with, but I didn't want to let your
message go un-replied-to.
I think the idea of putting globals into a per-sim struct is great.
This seems unobjectionable to me.
For the rest, I don't really know, though it seems basically reasonable.
Tom
next prev parent reply other threads:[~2010-07-08 20:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 22:30 Kevin Buettner
2010-07-08 20:08 ` Tom Tromey [this message]
2010-07-27 23:07 ` Kevin Buettner
2010-07-27 23:14 ` Pedro Alves
2010-07-27 23:31 ` Kevin Buettner
2010-08-03 12:05 ` Pedro Alves
2010-08-06 23:21 ` Kevin Buettner
2010-08-08 16:43 ` Pedro Alves
2010-08-10 0:21 ` Kevin Buettner
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=m38w5l68jt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).