kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@amd.com>
To: "Chenyi Qiang" <chenyi.qiang@intel.com>,
	"David Hildenbrand" <david@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Gupta Pankaj" <pankaj.gupta@amd.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Michael Roth" <michael.roth@amd.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Williams Dan J <dan.j.williams@intel.com>,
	Peng Chao P <chao.p.peng@intel.com>,
	Gao Chao <chao.gao@intel.com>, Xu Yilun <yilun.xu@intel.com>,
	Li Xiaoyao <xiaoyao.li@intel.com>
Subject: Re: [PATCH v4 01/13] memory: Export a helper to get intersection of a MemoryRegionSection with a given range
Date: Wed, 9 Apr 2025 16:45:43 +1000	[thread overview]
Message-ID: <0045ea05-3af5-4f07-84d5-546b0bc8bb91@amd.com> (raw)
In-Reply-To: <47b04426-73c7-41d9-b7b7-ee2fa40886ae@intel.com>



On 9/4/25 16:26, Chenyi Qiang wrote:
> 
> 
> On 4/9/2025 10:47 AM, Alexey Kardashevskiy wrote:
>>
>> On 7/4/25 17:49, Chenyi Qiang wrote:
>>> Rename the helper to memory_region_section_intersect_range() to make it
>>> more generic. Meanwhile, define the @end as Int128 and replace the
>>> related operations with Int128_* format since the helper is exported as
>>> a wider API.
>>>
>>> Suggested-by: Alexey Kardashevskiy <aik@amd.com>
>>> Reviewed-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Chenyi Qiang <chenyi.qiang@intel.com>
>>
>> ./scripts/checkpatch.pl complains "WARNING: line over 80 characters"
>>
>> with that fixed,
> 
> I observed many places in QEMU ignore the WARNING for over 80
> characters, so I also ignored them in my series.
> 
> After checking the rule in docs/devel/style.rst, I think I should try
> best to make it not longer than 80. But if it is hard to do so due to
> long function or symbol names, it is acceptable to not wrap it.
 >
> Then, I would modify the first warning code. For the latter two
> warnings, see code below
> 
>>
>> Reviewed-by: Alexey Kardashevskiy <aik@amd.com>
>>
>>> ---
>>> Changes in v4:
>>>       - No change.
>>>
>>> Changes in v3:
>>>       - No change
>>>
>>> Changes in v2:
>>>       - Make memory_region_section_intersect_range() an inline function.
>>>       - Add Reviewed-by from David
>>>       - Define the @end as Int128 and use the related Int128_* ops as a
>>> wilder
>>>         API (Alexey)
>>> ---
>>>    hw/virtio/virtio-mem.c | 32 +++++---------------------------
>>>    include/exec/memory.h  | 27 +++++++++++++++++++++++++++
>>>    2 files changed, 32 insertions(+), 27 deletions(-)
>>>
>>> diff --git a/hw/virtio/virtio-mem.c b/hw/virtio/virtio-mem.c
>>> index b1a003736b..21f16e4912 100644
>>> --- a/hw/virtio/virtio-mem.c
>>> +++ b/hw/virtio/virtio-mem.c
>>> @@ -244,28 +244,6 @@ static int
>>> virtio_mem_for_each_plugged_range(VirtIOMEM *vmem, void *arg,
>>>        return ret;
>>>    }
>>>    -/*
>>> - * Adjust the memory section to cover the intersection with the given
>>> range.
>>> - *
>>> - * Returns false if the intersection is empty, otherwise returns true.
>>> - */
>>> -static bool virtio_mem_intersect_memory_section(MemoryRegionSection *s,
>>> -                                                uint64_t offset,
>>> uint64_t size)
>>> -{
>>> -    uint64_t start = MAX(s->offset_within_region, offset);
>>> -    uint64_t end = MIN(s->offset_within_region + int128_get64(s->size),
>>> -                       offset + size);
>>> -
>>> -    if (end <= start) {
>>> -        return false;
>>> -    }
>>> -
>>> -    s->offset_within_address_space += start - s->offset_within_region;
>>> -    s->offset_within_region = start;
>>> -    s->size = int128_make64(end - start);
>>> -    return true;
>>> -}
>>> -
>>>    typedef int (*virtio_mem_section_cb)(MemoryRegionSection *s, void
>>> *arg);
>>>      static int virtio_mem_for_each_plugged_section(const VirtIOMEM *vmem,
>>> @@ -287,7 +265,7 @@ static int
>>> virtio_mem_for_each_plugged_section(const VirtIOMEM *vmem,
>>>                                          first_bit + 1) - 1;
>>>            size = (last_bit - first_bit + 1) * vmem->block_size;
>>>    -        if (!virtio_mem_intersect_memory_section(&tmp, offset,
>>> size)) {
>>> +        if (!memory_region_section_intersect_range(&tmp, offset,
>>> size)) {
>>>                break;
>>>            }
>>>            ret = cb(&tmp, arg);
>>> @@ -319,7 +297,7 @@ static int
>>> virtio_mem_for_each_unplugged_section(const VirtIOMEM *vmem,
>>>                                     first_bit + 1) - 1;
>>>            size = (last_bit - first_bit + 1) * vmem->block_size;
>>>    -        if (!virtio_mem_intersect_memory_section(&tmp, offset,
>>> size)) {
>>> +        if (!memory_region_section_intersect_range(&tmp, offset,
>>> size)) {
>>>                break;
>>>            }
>>>            ret = cb(&tmp, arg);
>>> @@ -355,7 +333,7 @@ static void virtio_mem_notify_unplug(VirtIOMEM
>>> *vmem, uint64_t offset,
>>>        QLIST_FOREACH(rdl, &vmem->rdl_list, next) {
>>>            MemoryRegionSection tmp = *rdl->section;
>>>    -        if (!virtio_mem_intersect_memory_section(&tmp, offset,
>>> size)) {
>>> +        if (!memory_region_section_intersect_range(&tmp, offset,
>>> size)) {
>>>                continue;
>>>            }
>>>            rdl->notify_discard(rdl, &tmp);
>>> @@ -371,7 +349,7 @@ static int virtio_mem_notify_plug(VirtIOMEM *vmem,
>>> uint64_t offset,
>>>        QLIST_FOREACH(rdl, &vmem->rdl_list, next) {
>>>            MemoryRegionSection tmp = *rdl->section;
>>>    -        if (!virtio_mem_intersect_memory_section(&tmp, offset,
>>> size)) {
>>> +        if (!memory_region_section_intersect_range(&tmp, offset,
>>> size)) {
>>>                continue;
>>>            }
>>>            ret = rdl->notify_populate(rdl, &tmp);
>>> @@ -388,7 +366,7 @@ static int virtio_mem_notify_plug(VirtIOMEM *vmem,
>>> uint64_t offset,
>>>                if (rdl2 == rdl) {
>>>                    break;
>>>                }
>>> -            if (!virtio_mem_intersect_memory_section(&tmp, offset,
>>> size)) {
>>> +            if (!memory_region_section_intersect_range(&tmp, offset,
>>> size)) {
>>>                    continue;
>>>                }
>>>                rdl2->notify_discard(rdl2, &tmp);
>>> diff --git a/include/exec/memory.h b/include/exec/memory.h
>>> index 3ee1901b52..3bebc43d59 100644
>>> --- a/include/exec/memory.h
>>> +++ b/include/exec/memory.h
>>> @@ -1202,6 +1202,33 @@ MemoryRegionSection
>>> *memory_region_section_new_copy(MemoryRegionSection *s);
>>>     */
>>>    void memory_region_section_free_copy(MemoryRegionSection *s);
>>>    +/**
>>> + * memory_region_section_intersect_range: Adjust the memory section
>>> to cover
>>> + * the intersection with the given range.
>>> + *
>>> + * @s: the #MemoryRegionSection to be adjusted
>>> + * @offset: the offset of the given range in the memory region
>>> + * @size: the size of the given range
>>> + *
>>> + * Returns false if the intersection is empty, otherwise returns true.
>>> + */
>>> +static inline bool
>>> memory_region_section_intersect_range(MemoryRegionSection *s,
>>> +                                                         uint64_t
>>> offset, uint64_t size)
>>> +{
>>> +    uint64_t start = MAX(s->offset_within_region, offset);
>>> +    Int128 end = int128_min(int128_add(int128_make64(s-
>>>> offset_within_region), s->size),
>>> +                            int128_add(int128_make64(offset),
>>> int128_make64(size)));
> 
> The Int128_* format helper make the line over 80. I think it's better
> not wrap it for readability.

I'd just reduce indent to previous line + 4 spaces vs the current "under 
the opening bracket" rule which I dislike anyway :) Thanks,


>>> +
>>> +    if (int128_le(end, int128_make64(start))) {
>>> +        return false;
>>> +    }
>>> +
>>> +    s->offset_within_address_space += start - s->offset_within_region;
>>> +    s->offset_within_region = start;
>>> +    s->size = int128_sub(end, int128_make64(start));
>>> +    return true;
>>> +}
>>> +
>>>    /**
>>>     * memory_region_init: Initialize a memory region
>>>     *
>>
> 

-- 
Alexey


  reply	other threads:[~2025-04-09  6:45 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  7:49 [PATCH v4 00/13] Enable shared device assignment Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 01/13] memory: Export a helper to get intersection of a MemoryRegionSection with a given range Chenyi Qiang
2025-04-09  2:47   ` Alexey Kardashevskiy
2025-04-09  6:26     ` Chenyi Qiang
2025-04-09  6:45       ` Alexey Kardashevskiy [this message]
2025-04-09  7:38         ` Chenyi Qiang
2025-05-12  3:24   ` Zhao Liu
2025-04-07  7:49 ` [PATCH v4 02/13] memory: Change memory_region_set_ram_discard_manager() to return the result Chenyi Qiang
2025-04-07  9:53   ` Xiaoyao Li
2025-04-08  0:50     ` Chenyi Qiang
2025-04-09  5:35   ` Alexey Kardashevskiy
2025-04-09  5:52     ` Chenyi Qiang
2025-04-25 12:35       ` David Hildenbrand
2025-04-07  7:49 ` [PATCH v4 03/13] memory: Unify the definiton of ReplayRamPopulate() and ReplayRamDiscard() Chenyi Qiang
2025-04-09  5:43   ` Alexey Kardashevskiy
2025-04-09  6:56     ` Chenyi Qiang
2025-04-25 12:44     ` David Hildenbrand
2025-04-25 12:42   ` David Hildenbrand
2025-04-27  2:13     ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 04/13] memory: Introduce generic state change parent class for RamDiscardManager Chenyi Qiang
2025-04-09  9:56   ` Alexey Kardashevskiy
2025-04-09 12:57     ` Chenyi Qiang
2025-04-10  0:11       ` Alexey Kardashevskiy
2025-04-10  1:44         ` Chenyi Qiang
2025-04-16  3:32           ` Chenyi Qiang
2025-04-17 23:10             ` Alexey Kardashevskiy
2025-04-18  3:49               ` Chenyi Qiang
2025-04-25 12:54             ` David Hildenbrand
2025-04-25 12:49     ` David Hildenbrand
2025-04-27  1:33       ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 05/13] memory: Introduce PrivateSharedManager Interface as child of GenericStateManager Chenyi Qiang
2025-04-09  9:56   ` Alexey Kardashevskiy
2025-04-10  3:47     ` Chenyi Qiang
2025-04-25 12:57   ` David Hildenbrand
2025-04-27  1:40     ` Chenyi Qiang
2025-04-29 10:01       ` David Hildenbrand
2025-04-07  7:49 ` [PATCH v4 06/13] vfio: Add the support for PrivateSharedManager Interface Chenyi Qiang
2025-04-09  9:58   ` Alexey Kardashevskiy
2025-04-10  5:53     ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 07/13] ram-block-attribute: Introduce RamBlockAttribute to manage RAMBLock with guest_memfd Chenyi Qiang
2025-04-09  9:57   ` Alexey Kardashevskiy
2025-04-10  7:37     ` Chenyi Qiang
2025-05-09  6:41   ` Baolu Lu
2025-05-09  7:55     ` Chenyi Qiang
2025-05-09  8:18       ` David Hildenbrand
2025-05-09 10:37         ` Chenyi Qiang
2025-05-12  8:07   ` Zhao Liu
2025-05-12  9:43     ` Chenyi Qiang
2025-05-13  8:31       ` Zhao Liu
2025-05-14  1:39         ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 08/13] ram-block-attribute: Introduce a callback to notify shared/private state changes Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 09/13] memory: Attach RamBlockAttribute to guest_memfd-backed RAMBlocks Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 10/13] memory: Change NotifyStateClear() definition to return the result Chenyi Qiang
2025-04-27  2:26   ` Chenyi Qiang
2025-05-09  2:38     ` Chao Gao
2025-05-09  8:20       ` David Hildenbrand
2025-05-09  9:19         ` Chenyi Qiang
2025-05-09  8:22     ` Baolu Lu
2025-05-09 10:04       ` Chenyi Qiang
2025-05-12  7:54         ` David Hildenbrand
2025-04-07  7:49 ` [PATCH v4 11/13] KVM: Introduce CVMPrivateSharedListener for attribute changes during page conversions Chenyi Qiang
2025-05-09  9:03   ` Baolu Lu
2025-05-12  3:18     ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 12/13] ram-block-attribute: Add priority listener support for PrivateSharedListener Chenyi Qiang
2025-05-09  9:23   ` Baolu Lu
2025-05-09  9:39     ` Chenyi Qiang
2025-04-07  7:49 ` [PATCH v4 13/13] RAMBlock: Make guest_memfd require coordinate discard Chenyi Qiang

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=0045ea05-3af5-4f07-84d5-546b0bc8bb91@amd.com \
    --to=aik@amd.com \
    --cc=chao.gao@intel.com \
    --cc=chao.p.peng@intel.com \
    --cc=chenyi.qiang@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pankaj.gupta@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoyao.li@intel.com \
    --cc=yilun.xu@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).