From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Laurent Vivier <laurent@vivier.eu>,
Thomas Huth <thuth@redhat.com>, Warner Losh <imp@bsdimp.com>,
Kyle Evans <kevans@freebsd.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [RFC PATCH 0/5] Deprecate/rename singlestep command line option
Date: Mon, 6 Feb 2023 08:18:34 -1000 [thread overview]
Message-ID: <8225a961-c59e-041e-41e4-a885b417b9aa@linaro.org> (raw)
In-Reply-To: <20230206171359.1327671-1-peter.maydell@linaro.org>
On 2/6/23 07:13, Peter Maydell wrote:
> So, questions:
>
> (1) is this worth bothering with at all? We could just
> name our global variable etc better, and document what
> -singlestep actually does, and not bother with the new
> names for the options/commands.
> (2) if we do do it, do we retain the old name indefinitely,
> or actively put it on the deprecate-and-drop list?
> (3) what should we do about the HMP StatusInfo object?
> I'm not sure how we handle compatibility for HMP.
I was thinking that a better place to put this is within -d, akin to nochain.
I would deprecate and drop. I dunno what to do about HMP.
r~
next prev parent reply other threads:[~2023-02-06 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:13 [RFC PATCH 0/5] Deprecate/rename singlestep command line option Peter Maydell
2023-02-06 17:13 ` [RFC PATCH 1/5] Rename the singlestep global variable to one_insn_per_tb Peter Maydell
2023-02-06 20:20 ` Thomas Huth
2023-02-10 16:48 ` Peter Maydell
2023-02-06 17:13 ` [RFC PATCH 2/5] linux-user: Add '-one-insn-per-tb' option equivalent to '-singlestep' Peter Maydell
2023-02-06 17:13 ` [RFC PATCH 3/5] bsd-user: " Peter Maydell
2023-02-06 17:13 ` [RFC PATCH 4/5] softmmu: " Peter Maydell
2023-02-06 17:13 ` [RFC PATCH 5/5] hmp: Add 'one-insn-per-tb' command equivalent to 'singlestep' Peter Maydell
2023-02-06 18:18 ` Richard Henderson [this message]
2023-02-06 20:17 ` [RFC PATCH 0/5] Deprecate/rename singlestep command line option Thomas Huth
2023-02-07 11:01 ` Peter Maydell
2023-02-07 11:33 ` Thomas Huth
2023-02-07 15:56 ` Markus Armbruster
2023-02-08 23:04 ` Warner Losh
2023-02-13 15:01 ` Dr. David Alan Gilbert
2023-04-03 12:47 ` Peter Maydell
2023-04-03 14:41 ` Markus Armbruster
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=8225a961-c59e-041e-41e4-a885b417b9aa@linaro.org \
--to=richard.henderson@linaro.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 NNTP newsgroup(s).