From: Bruce Rogers <brogers@suse.com>
To: David Hildenbrand <david@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] virtio-mem: Work around format specifier mismatch for RISC-V
Date: Thu, 30 Jul 2020 06:51:46 -0600 [thread overview]
Message-ID: <1b00c0e25ec65e113d4c7fa98b1466689f05a986.camel@suse.com> (raw)
In-Reply-To: <afd9a33f-8bfe-e4e5-64fe-c41da91d9d54@redhat.com>
On Thu, 2020-07-30 at 10:12 +0200, David Hildenbrand wrote:
> On 30.07.20 09:58, Stefano Garzarella wrote:
> > On Thu, Jul 30, 2020 at 09:51:19AM +0200, David Hildenbrand wrote:
> > > On 30.07.20 09:49, Stefano Garzarella wrote:
> > > > On Wed, Jul 29, 2020 at 06:54:38PM -0600, Bruce Rogers wrote:
> > > > > This likely affects other, less popular host architectures as
> > > > > well.
> > > > > Less common host architectures under linux get
> > > > > QEMU_VMALLOC_ALIGN (from
> > > > > which VIRTIO_MEM_MIN_BLOCK_SIZE is derived) define to a
> > > > > variable of
> > > > > type uintptr, which isn't compatible with the format
> > > > > specifier used to
> > > > > print a user message. Since this particular usage of the
> > > > > underlying data
> > > > > seems unique, the simple fix is to just cast it to the
> > > > > corresponding
> > > > > format specifier.
> > > > >
> > > > > Signed-off-by: Bruce Rogers <brogers@suse.com>
> > > > > ---
> > > > > hw/virtio/virtio-mem.c | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
> > > > > index c12e9f79b0..fd01ffd83e 100644
> > > > > --- a/hw/virtio/virtio-mem.c
> > > > > +++ b/hw/virtio/virtio-mem.c
> > > > > @@ -754,7 +754,7 @@ static void
> > > > > virtio_mem_set_block_size(Object *obj, Visitor *v, const char
> > > > > *name,
> > > > >
> > > > > if (value < VIRTIO_MEM_MIN_BLOCK_SIZE) {
> > > > > error_setg(errp, "'%s' property has to be at least
> > > > > 0x%" PRIx32, name,
> > > > > - VIRTIO_MEM_MIN_BLOCK_SIZE);
> > > > > + (unsigned int)VIRTIO_MEM_MIN_BLOCK_SIZE);
> > > >
> > > > Since we use PRIx32, could be better to cast
> > > > VIRTIO_MEM_MIN_BLOCK_SIZE
> > > > to uint32_t?
> > >
> > > Yeah, I guess something like
> > >
> > > -#define VIRTIO_MEM_MIN_BLOCK_SIZE QEMU_VMALLOC_ALIGN
> > > +#define VIRTIO_MEM_MIN_BLOCK_SIZE ((uint32_t)QEMU_VMALLOC_ALIGN)
> > >
> > > would be cleaner
> >
> > Yeah, it is cleaner.
>
> Bruce, can you respin if you agree? Thanks!
>
Agreed.
- Bruce
prev parent reply other threads:[~2020-07-30 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 0:54 [PATCH] virtio-mem: Work around format specifier mismatch for RISC-V Bruce Rogers
2020-07-30 7:49 ` Stefano Garzarella
2020-07-30 7:51 ` David Hildenbrand
2020-07-30 7:58 ` Stefano Garzarella
2020-07-30 8:12 ` David Hildenbrand
2020-07-30 12:51 ` Bruce Rogers [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=1b00c0e25ec65e113d4c7fa98b1466689f05a986.camel@suse.com \
--to=brogers@suse.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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).