All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhao Liu <zhao1.liu@linux.intel.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [RFC] util/error-report: Add "error: " prefix for error-level report
Date: Wed, 27 Mar 2024 21:02:30 +0800	[thread overview]
Message-ID: <ZgQY5rQVQJH0Its9@intel.com> (raw)
In-Reply-To: <a2d13494-aec2-427b-af9b-e8c41f7057f1@redhat.com>

On Wed, Mar 27, 2024 at 01:36:07PM +0100, Thomas Huth wrote:

[snip]

> Sounds like a good idea to me, but I think you should then also remove
> the hard-coded "error:" strings in the various error_reports():

Thanks Thomas! I missed this case, will remove these hard-code prefix
first.

> $ grep -ri 'error_report.*"error:'
> migration/block-dirty-bitmap.c:        error_report("Error: block device name is not set");
> migration/block-dirty-bitmap.c:                error_report("Error: Unknown bitmap alias '%s' on node "
> migration/block-dirty-bitmap.c:                error_report("Error: unknown dirty bitmap "
> migration/block-dirty-bitmap.c:        error_report("Error: block device name is not set");
> target/i386/kvm/kvm.c:        error_report("error: failed to set MSR 0x%" PRIx32 " to 0x%" PRIx64,
> target/i386/kvm/kvm.c:        error_report("error: failed to get MSR 0x%" PRIx32,
> util/vhost-user-server.c:        error_report("Error: too big message request: %d, "
> accel/hvf/hvf-all.c:        error_report("Error: HV_ERROR");
> accel/hvf/hvf-all.c:        error_report("Error: HV_BUSY");
> accel/hvf/hvf-all.c:        error_report("Error: HV_BAD_ARGUMENT");
> accel/hvf/hvf-all.c:        error_report("Error: HV_NO_RESOURCES");
> accel/hvf/hvf-all.c:        error_report("Error: HV_NO_DEVICE");
> accel/hvf/hvf-all.c:        error_report("Error: HV_UNSUPPORTED");
> accel/hvf/hvf-all.c:        error_report("Error: HV_DENIED");
> monitor/hmp-cmds.c:        error_reportf_err(err, "Error: ");
> hw/arm/xlnx-zcu102.c:        error_report("ERROR: RAM size 0x%" PRIx64 " above max supported of "
> hw/block/dataplane/xen-block.c:        error_report("error: unknown operation (%d)", request->req.operation);
> hw/block/dataplane/xen-block.c:        error_report("error: write req for ro device");
> hw/block/dataplane/xen-block.c:            error_report("error: nr_segments too big");
> hw/block/dataplane/xen-block.c:            error_report("error: first > last sector");
> hw/block/dataplane/xen-block.c:            error_report("error: page crossing");
> hw/block/dataplane/xen-block.c:        error_report("error: access beyond end of file");
> hw/rdma/rdma_backend.c:            rdma_error_report("Error: Not a MAD request, skipping");
> hw/s390x/s390-skeys.c:        error_report("Error: Setting storage keys for pages with unallocated "
> hw/s390x/s390-skeys.c:        error_report("Error: Getting storage keys for pages with unallocated "
> hw/usb/bus.c:        error_report("Error: no usb bus to attach usbdevice %s, "
> gdbstub/gdbstub.c:            error_report("Error: Bad gdb register numbering for '%s', "
> 
>  Thomas
> 
> 


  reply	other threads:[~2024-03-27 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 11:46 [RFC] util/error-report: Add "error: " prefix for error-level report Zhao Liu
2024-03-27 12:36 ` Thomas Huth
2024-03-27 13:02   ` Zhao Liu [this message]
2024-03-29 11:10   ` Paolo Bonzini
2024-03-29 17:15     ` Zhao Liu

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=ZgQY5rQVQJH0Its9@intel.com \
    --to=zhao1.liu@linux.intel.com \
    --cc=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.