qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Yao Xingtao <yaoxt.fnst@fujitsu.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org
Subject: Re: [PATCH 02/13] arm/boot: make range overlap check more readable
Date: Mon, 22 Jul 2024 08:54:54 +0200	[thread overview]
Message-ID: <42f92293-2c7e-4ab0-920d-f81da79f550c@linaro.org> (raw)
In-Reply-To: <20240722040742.11513-3-yaoxt.fnst@fujitsu.com>

On 22/7/24 06:07, Yao Xingtao via wrote:
> use ranges_overlap() instead of open-coding the overlap check to improve
> the readability of the code.
> 
> Signed-off-by: Yao Xingtao <yaoxt.fnst@fujitsu.com>
> ---
>   hw/arm/boot.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/arm/boot.c b/hw/arm/boot.c
> index d480a7da02cf..a004a90e87be 100644
> --- a/hw/arm/boot.c
> +++ b/hw/arm/boot.c
> @@ -26,6 +26,7 @@
>   #include "qemu/config-file.h"
>   #include "qemu/option.h"
>   #include "qemu/units.h"
> +#include "qemu/range.h"
>   
>   /* Kernel boot protocol is specified in the kernel docs
>    * Documentation/arm/Booting and Documentation/arm64/booting.txt
> @@ -238,8 +239,8 @@ void arm_write_secure_board_setup_dummy_smc(ARMCPU *cpu,
>       assert((mvbar_addr & 0x1f) == 0 && (mvbar_addr >> 4) < 0x100);
>   
>       /* check that these blobs don't overlap */
> -    assert((mvbar_addr + sizeof(mvbar_blob) <= info->board_setup_addr)
> -          || (info->board_setup_addr + sizeof(board_setup_blob) <= mvbar_addr));
> +    assert(!ranges_overlap(mvbar_addr, sizeof(mvbar_blob),
> +           info->board_setup_addr, sizeof(board_setup_blob)));

Indentation is of, otherwise:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>



  reply	other threads:[~2024-07-22  6:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-22  4:07 [PATCH 00/13] make range overlap check more readable Yao Xingtao via
2024-07-22  4:07 ` [PATCH 01/13] range: Make ranges_overlap() return bool Yao Xingtao via
2024-07-22  6:54   ` Philippe Mathieu-Daudé
2024-07-22  4:07 ` [PATCH 02/13] arm/boot: make range overlap check more readable Yao Xingtao via
2024-07-22  6:54   ` Philippe Mathieu-Daudé [this message]
2024-07-22  4:07 ` [PATCH 03/13] core/loader: " Yao Xingtao via
2024-07-22  4:07 ` [PATCH 04/13] cxl/mailbox: " Yao Xingtao via
2024-07-22  6:56   ` Philippe Mathieu-Daudé
2024-07-22  4:07 ` [PATCH 05/13] display/sm501: " Yao Xingtao via
2024-07-22  4:07 ` [PATCH 06/13] aspeed_smc: " Yao Xingtao via
2024-07-22  7:11   ` Philippe Mathieu-Daudé
2024-07-22  4:07 ` [PATCH 07/13] qtest/fuzz: " Yao Xingtao via
2024-07-22  5:03   ` Alexander Bulekov
2024-07-22  7:10   ` Philippe Mathieu-Daudé
2024-07-22  4:07 ` [PATCH 08/13] sparc/ldst_helper: " Yao Xingtao via
2024-07-22 12:18   ` Philippe Mathieu-Daudé
2024-07-22  4:07 ` [PATCH 09/13] system/memory_mapping: " Yao Xingtao via
2024-07-22  7:21   ` Philippe Mathieu-Daudé
2024-07-22  9:13   ` David Hildenbrand
2024-07-22  4:07 ` [PATCH 10/13] block/vhdx: " Yao Xingtao via
2024-07-22  4:07 ` [PATCH 11/13] crypto/block-luks: " Yao Xingtao via
2024-07-22  7:13   ` Philippe Mathieu-Daudé
2024-07-22  7:57   ` Daniel P. Berrangé
2024-07-22  4:07 ` [PATCH 12/13] dump: " Yao Xingtao via
2024-07-22  7:01   ` Marc-André Lureau
2024-07-22  4:07 ` [PATCH 13/13] block/qcow2-cluster: " Yao Xingtao via
2024-08-20  3:15   ` Xingtao Yao (Fujitsu) via
2024-07-22  6:42 ` [PATCH 00/13] " Philippe Mathieu-Daudé
2024-07-22  6:59   ` Xingtao Yao (Fujitsu) via
2024-07-22  7:37     ` Philippe Mathieu-Daudé
2024-07-22  7:40       ` Xingtao Yao (Fujitsu) via
2024-09-07  5:50         ` Philippe Mathieu-Daudé
2024-07-25 15:13     ` Peter Maydell
2024-07-26  0:16       ` Xingtao Yao (Fujitsu) via
2024-07-26  9:37         ` Peter Maydell

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=42f92293-2c7e-4ab0-920d-f81da79f550c@linaro.org \
    --to=philmd@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yaoxt.fnst@fujitsu.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).