qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Xiaoyao Li" <xiaoyao.li@intel.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Xu" <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
	Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] physmem: replace function name with __func__ in ram_block_discard_range()
Date: Thu, 25 Jan 2024 09:22:30 +0100	[thread overview]
Message-ID: <7d586878-4b0d-401d-a706-9d18ffd52435@redhat.com> (raw)
In-Reply-To: <9943c88e-3ccd-4a3b-bbe0-65a8a58755d1@linaro.org>

On 25.01.24 06:06, Philippe Mathieu-Daudé wrote:
> Hi,
> 
> On 25/1/24 03:33, Xiaoyao Li wrote:
>> Use __func__ to avoid hard-coded function name.
>>
>> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>> ---
>>    system/physmem.c | 38 +++++++++++++++++---------------------
>>    1 file changed, 17 insertions(+), 21 deletions(-)
> 
> 
>>        if ((start + length) <= rb->max_length) {
>>            bool need_madvise, need_fallocate;
>>            if (!QEMU_IS_ALIGNED(length, rb->page_size)) {
>> -            error_report("ram_block_discard_range: Unaligned length: %zx",
>> -                         length);
>> +            error_report("%s: Unaligned length: %zx", __func__, length);
> 
> Pre-existing, should we enforce 0x prefix for %*x format?

Likely yes, but then, most of these errors here are more similar to 
assertions that we never ever see unless we have real bugs in QEMU. So I 
wouldn't lose sleep over it.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-01-25  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  2:33 [PATCH] physmem: replace function name with __func__ in ram_block_discard_range() Xiaoyao Li
2024-01-25  5:06 ` Philippe Mathieu-Daudé
2024-01-25  8:22   ` David Hildenbrand [this message]
2024-01-25 10:35 ` Paolo Bonzini

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=7d586878-4b0d-401d-a706-9d18ffd52435@redhat.com \
    --to=david@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    --cc=xiaoyao.li@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;
as well as URLs for NNTP newsgroup(s).