From: Peter Maydell <peter.maydell@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, philmd@linaro.org
Subject: Re: [PATCH 2/2] log: Suggest using -d guest_error,memaccess instead of guest_errors
Date: Mon, 14 Oct 2024 15:18:02 +0100 [thread overview]
Message-ID: <CAFEAcA_1ejDprH6H=EPoP59jweUkuaZR_mcuNhhGFmDiQBNKMg@mail.gmail.com> (raw)
In-Reply-To: <0f5949d8ece522e30f990d25981f79965bf05bbf.1728232526.git.balaton@eik.bme.hu>
On Sun, 6 Oct 2024 at 17:49, BALATON Zoltan <balaton@eik.bme.hu> wrote:
>
> Rename guest_errors to guest_error to match the log constant
I don't think this is a good reason to change the user-facing
behaviour. Also, I don't think the existing names are so bad:
-d guest_errors
this is plural because we are asking to log all guest errors
qemu_log_mask(LOG_GUEST_ERROR, ...)
this is singular because we are logging a single error here.
If we do want to change things for consistency, we should decide
on what the user-facing option name ought to be (and I think
plural is fine), and then change the internal define to match
that, not vice versa.
> and print
> a warning for -d guest_errors to remind using guest_error,memaccess
> instead but preserve previous behaviour for convenience.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
thanks
-- PMM
next prev parent reply other threads:[~2024-10-14 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 16:49 [PATCH 0/2] Separate memory access logs from guest_errors BALATON Zoltan
2024-10-06 16:49 ` [PATCH 1/2] log: Add separate debug option for logging invalid memory accesses BALATON Zoltan
2024-10-14 14:13 ` Peter Maydell
2024-10-14 16:48 ` BALATON Zoltan
2024-10-06 16:49 ` [PATCH 2/2] log: Suggest using -d guest_error,memaccess instead of guest_errors BALATON Zoltan
2024-10-14 14:18 ` Peter Maydell [this message]
2024-10-14 16:46 ` BALATON Zoltan
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='CAFEAcA_1ejDprH6H=EPoP59jweUkuaZR_mcuNhhGFmDiQBNKMg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=philmd@linaro.org \
--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).