public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Ani Sinha <anisinha@redhat.com>,
	 Paolo Bonzini <pbonzini@redhat.com>,
	qemu-trivial@nongnu.org,  zhao1.liu@intel.com,
	 kvm@vger.kernel.org, qemu-devel@nongnu.org,
	 Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v3] kvm: replace fprintf with error_report/printf() in kvm_init()
Date: Tue, 27 Aug 2024 08:30:36 +0200	[thread overview]
Message-ID: <87v7zmmq9f.fsf@pond.sub.org> (raw)
In-Reply-To: <8913b8c7-4103-4f69-8567-afdc29f8d0d3@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Fri, 9 Aug 2024 10:35:57 +0200")

Philippe Mathieu-Daudé <philmd@linaro.org> writes:

> Hi Ani,
>
> On 9/8/24 08:49, Ani Sinha wrote:
>> error_report() is more appropriate for error situations. Replace fprintf with
>> error_report. Cosmetic. No functional change.
>> CC: qemu-trivial@nongnu.org
>> CC: zhao1.liu@intel.com
>
> (Pointless to carry Cc line when patch is already reviewed next line)
>
>> Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
>> Signed-off-by: Ani Sinha <anisinha@redhat.com>
>> ---
>>   accel/kvm/kvm-all.c | 40 ++++++++++++++++++----------------------
>>   1 file changed, 18 insertions(+), 22 deletions(-)
>> changelog:
>> v2: fix a bug.
>> v3: replace one instance of error_report() with error_printf(). added tags.
>> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
>> index 75d11a07b2..5bc9d35b61 100644
>> --- a/accel/kvm/kvm-all.c
>> +++ b/accel/kvm/kvm-all.c
>> @@ -2427,7 +2427,7 @@ static int kvm_init(MachineState *ms)
>>       QLIST_INIT(&s->kvm_parked_vcpus);
>>       s->fd = qemu_open_old(s->device ?: "/dev/kvm", O_RDWR);
>>       if (s->fd == -1) {
>> -        fprintf(stderr, "Could not access KVM kernel module: %m\n");
>> +        error_report("Could not access KVM kernel module: %m");
>>           ret = -errno;
>>           goto err;
>>       }
>> @@ -2437,13 +2437,13 @@ static int kvm_init(MachineState *ms)
>>           if (ret >= 0) {
>>               ret = -EINVAL;
>>           }
>> -        fprintf(stderr, "kvm version too old\n");
>> +        error_report("kvm version too old");
>>           goto err;
>>       }
>>         if (ret > KVM_API_VERSION) {
>>           ret = -EINVAL;
>> -        fprintf(stderr, "kvm version not supported\n");
>> +        error_report("kvm version not supported");
>>           goto err;
>>       }
>>   @@ -2488,26 +2488,22 @@ static int kvm_init(MachineState *ms)
>>       } while (ret == -EINTR);
>>         if (ret < 0) {
>> -        fprintf(stderr, "ioctl(KVM_CREATE_VM) failed: %d %s\n", -ret,
>> -                strerror(-ret));
>> +        error_report("ioctl(KVM_CREATE_VM) failed: %d %s", -ret,
>> +                    strerror(-ret));
>>     #ifdef TARGET_S390X
>>           if (ret == -EINVAL) {
>> -            fprintf(stderr,
>> -                    "Host kernel setup problem detected. Please verify:\n");
>> -            fprintf(stderr, "- for kernels supporting the switch_amode or"
>> -                    " user_mode parameters, whether\n");
>> -            fprintf(stderr,
>> -                    "  user space is running in primary address space\n");
>> -            fprintf(stderr,
>> -                    "- for kernels supporting the vm.allocate_pgste sysctl, "
>> -                    "whether it is enabled\n");
>> +            error_report("Host kernel setup problem detected.
>
> \n"
>
> Should we use error_printf_unless_qmp() for the following?
>
> " Please verify:");
>> +            error_report("- for kernels supporting the switch_amode or"
>> +                        " user_mode parameters, whether");
>> +            error_report("  user space is running in primary address space");
>> +            error_report("- for kernels supporting the vm.allocate_pgste "
>> +                        "sysctl, whether it is enabled");

Do not put newlines into error messages.  error_report()'s function
comment demands "The resulting message should be a single phrase, with
no newline or trailing punctuation."

You can do this:

    error_report(... the actual error message ...);
    error_printf(... hints on what to do about it ...);

Questions?

[...]


  parent reply	other threads:[~2024-08-27  6:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  6:49 [PATCH v3] kvm: replace fprintf with error_report/printf() in kvm_init() Ani Sinha
2024-08-09  8:35 ` Philippe Mathieu-Daudé
2024-08-12  9:53   ` Ani Sinha
     [not found]     ` <CAK3XEhPZ8X1-Ui6pJ+kYY3Er-N-zW0f5MqpLyaU7t2d3qaQXkA@mail.gmail.com>
2024-08-16  6:21       ` Philippe Mathieu-Daudé
2024-08-21  3:38         ` Ani Sinha
2024-08-27  6:30   ` Markus Armbruster [this message]
2024-08-27 12:17     ` Ani Sinha
2024-08-27 12:26       ` 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=87v7zmmq9f.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=zhao1.liu@intel.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