qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Akihiko Odaki <akihiko.odaki@daynix.com>
Subject: Re: [PATCH] util/cacheflush: Avoid flushing dcache twice when not necessary
Date: Tue, 6 Jun 2023 00:33:15 +0200	[thread overview]
Message-ID: <b59bde61-4c32-47fc-441d-8196654b7f7c@linaro.org> (raw)
In-Reply-To: <4aee6249-c5b2-5d21-c6e5-e995734ae518@eik.bme.hu>

On 5/6/23 23:56, BALATON Zoltan wrote:
> On Mon, 5 Jun 2023, Philippe Mathieu-Daudé wrote:
>> <libkern/OSCacheControl.h> describes sys_icache_invalidate() as
>> "equivalent to sys_cache_control(kCacheFunctionPrepareForExecution)",
>> having kCacheFunctionPrepareForExecution defined as:
>>
>>  /* Prepare memory for execution.  This should be called
>>   * after writing machine instructions to memory, before
>>   * executing them.  It syncs the dcache and icache. [...]
>>   */
>>
>> Since the dcache is also sync'd, we can avoid the sys_dcache_flush()
>> call when both rx/rw pointers are equal.
>>
>> Suggested-by: Richard Henderson <richard.henderson@linaro.org>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> Based-on: <20230605175647.88395-2-philmd@linaro.org>
>> ---
>> util/cacheflush.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/util/cacheflush.c b/util/cacheflush.c
>> index de35616718..a08906155a 100644
>> --- a/util/cacheflush.c
>> +++ b/util/cacheflush.c
>> @@ -241,7 +241,14 @@ static void __attribute__((constructor)) 
>> init_cache_info(void)
>>
>> void flush_idcache_range(uintptr_t rx, uintptr_t rw, size_t len)
>> {
>> -    sys_dcache_flush((void *)rw, len);
>> +    if (rx == rw) {
> 
> Isn't it more straight forward to use rx != rw and drop the else branch 
> than having an empty if branch? You can still keep the comment above the 
> if to explain it if needed.

I tried that first but found it was not obvious, so chose this
form because it seemed clearer to me.


      reply	other threads:[~2023-06-05 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05 19:59 [PATCH] util/cacheflush: Avoid flushing dcache twice when not necessary Philippe Mathieu-Daudé
2023-06-05 20:00 ` Philippe Mathieu-Daudé
2023-06-05 20:03 ` Richard Henderson
2023-06-05 21:56 ` BALATON Zoltan
2023-06-05 22:33   ` Philippe Mathieu-Daudé [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=b59bde61-4c32-47fc-441d-8196654b7f7c@linaro.org \
    --to=philmd@linaro.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=balaton@eik.bme.hu \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).