From: "Alex Bennée" <alex.bennee@linaro.org>
To: Moteen Shah <moteenshah.02@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v1] virtio/virtio.c: include virtio prefix in error message
Date: Fri, 15 Apr 2022 12:10:17 +0100 [thread overview]
Message-ID: <87lew6sipb.fsf@linaro.org> (raw)
In-Reply-To: <20220414112902.41390-1-codeguy.moteen@gmail.com>
Moteen Shah <moteenshah.02@gmail.com> writes:
> From: Moteen Shah <moteenshah.02@gmail.com>
>
> The error message in virtio_init_region_cache()
> is given a prefix virtio.
It seems a shame considering we have a common virtio_error function that
we couldn't do it in one place. One option would be to make virtio_error
a macro that could insert __func__ in place:
#define virtio_error(vdev, fmt, ...) \
virtio_error_impl(vdev, "%s: " fmt, __func__, ## __VA_ARGS__);
void virtio_error_impl(VirtIODevice *vdev, const char *fmt, ...) G_GNUC_PRINTF(2, 3);
and make rename the function in virtio.c. As the functions calling this
all tend to have virtio in their names anyway. What do you think?
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/230
> Buglink: https://bugs.launchpad.net/qemu/+bug/1919021``
>
> Signed-off-by: Moteen Shah <moteenshah.02@gmail.com>
> ---
> hw/virtio/virtio.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 9d637e043e..f31427bd41 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -174,7 +174,7 @@ static void virtio_init_region_cache(VirtIODevice *vdev, int n)
> len = address_space_cache_init(&new->desc, vdev->dma_as,
> addr, size, packed);
> if (len < size) {
> - virtio_error(vdev, "Cannot map desc");
> + virtio_error(vdev, "Virtio cannot map desc");
> goto err_desc;
> }
>
> @@ -182,7 +182,7 @@ static void virtio_init_region_cache(VirtIODevice *vdev, int n)
> len = address_space_cache_init(&new->used, vdev->dma_as,
> vq->vring.used, size, true);
> if (len < size) {
> - virtio_error(vdev, "Cannot map used");
> + virtio_error(vdev, "Virtio cannot map used");
> goto err_used;
> }
>
> @@ -190,7 +190,7 @@ static void virtio_init_region_cache(VirtIODevice *vdev, int n)
> len = address_space_cache_init(&new->avail, vdev->dma_as,
> vq->vring.avail, size, false);
> if (len < size) {
> - virtio_error(vdev, "Cannot map avail");
> + virtio_error(vdev, "Virtio cannot map avail");
> goto err_avail;
> }
--
Alex Bennée
prev parent reply other threads:[~2022-04-15 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 11:29 [PATCH v1] virtio/virtio.c: include virtio prefix in error message Moteen Shah
2022-04-15 11:10 ` Alex Bennée [this message]
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=87lew6sipb.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=moteenshah.02@gmail.com \
--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 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.