All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: <nifan.cxl@gmail.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
	<gregory.price@memverge.com>, <ira.weiny@intel.com>,
	<dan.j.williams@intel.com>, <a.manzanares@samsung.com>,
	<dave@stgolabs.net>, <nmtadam.samsung@gmail.com>,
	<jim.harris@samsung.com>, <Jorgen.Hansen@wdc.com>,
	<wj28.lee@gmail.com>, Fan Ni <fan.ni@samsung.com>
Subject: Re: [PATCH v5 11/13] hw/cxl/cxl-mailbox-utils: Add partial and superset extent release mailbox support
Date: Wed, 6 Mar 2024 18:09:46 +0000	[thread overview]
Message-ID: <20240306180946.00005161@Huawei.com> (raw)
In-Reply-To: <20240304194331.1586191-12-nifan.cxl@gmail.com>

On Mon,  4 Mar 2024 11:34:06 -0800
nifan.cxl@gmail.com wrote:

> From: Fan Ni <fan.ni@samsung.com>
> 
> With the change, we extend the extent release mailbox command processing
> to allow more flexible release. As long as the DPA range of the extent to
> release is covered by valid extent(s) in the device, the release can be
> performed.
> 
> Signed-off-by: Fan Ni <fan.ni@samsung.com>

Ouch this is more complex than I was thinking, but seems correct to me.

A few minor comments inline

Jonathan

> +/*
> + * Detect potential extent overflow caused by extent split during processing
> + * extent release requests, also allow releasing superset of extents where the
> + * extent to release covers the range of multiple extents in the device.
> + * Note:
> + * 1.we will reject releasing an extent if some portion of its rang is

range

> + * not covered by valid extents.
> + * 2.This function is called after cxl_detect_malformed_extent_list so checks
> + * already performed there will be skipped.
> + */
> +static CXLRetCode cxl_detect_extent_overflow(const CXLType3Dev *ct3d,
> +        const CXLUpdateDCExtentListInPl *in)

This code is basically dry running the actual removal.  Can we just
make the core code the same for both cases?  The bit where you update bitmaps
and extent lists at least.

> +{
> +    uint64_t nbits, offset;
> +    const CXLDCRegion *region;
> +    unsigned long **bitmaps_copied;
> +    uint64_t dpa, len;
> +    int i, rid;
> +    CXLRetCode ret = CXL_MBOX_SUCCESS;
> +    long extent_cnt_delta = 0;
> +    CXLDCExtentList tmp_list;
> +    CXLDCExtent *ent;
> +
> +    QTAILQ_INIT(&tmp_list);
> +    copy_extent_list(&tmp_list, &ct3d->dc.extents);
> +
> +    bitmaps_copied = g_new0(unsigned long *, ct3d->dc.num_regions);
> +    for (i = 0; i < ct3d->dc.num_regions; i++) {
> +        region = &ct3d->dc.regions[i];
> +        nbits = region->len / region->block_size;
> +        bitmaps_copied[i] = bitmap_new(nbits);
> +        bitmap_copy(bitmaps_copied[i], region->blk_bitmap, nbits);
> +    }
> +
> +    for (i = 0; i < in->num_entries_updated; i++) {
> +        dpa = in->updated_entries[i].start_dpa;
> +        len = in->updated_entries[i].len;
> +
> +        rid = cxl_find_dc_region_id(ct3d, dpa, len);
> +        region = &ct3d->dc.regions[rid];
> +        offset = (dpa - region->base) / region->block_size;
> +        nbits = len / region->block_size;
> +
> +        /* Check whether range [dpa, dpa + len) is covered by valid range */
> +        if (find_next_zero_bit(bitmaps_copied[rid], offset + nbits, offset) <
> +                               offset + nbits) {
> +            ret = CXL_MBOX_INVALID_PA;
> +            goto free_and_exit;
> +        }
> +
> +        QTAILQ_FOREACH(ent, &tmp_list, node) {
> +            /* Only split within an extent can cause extent count increase */
> +            if (ent->start_dpa <= dpa &&
> +                dpa + len <= ent->start_dpa + ent->len) {
> +                uint64_t ent_start_dpa = ent->start_dpa;
> +                uint64_t ent_len = ent->len;
> +                uint64_t len1 = dpa - ent_start_dpa;
> +                uint64_t len2 = ent_start_dpa + ent_len - dpa - len;
> +
> +                extent_cnt_delta += len1 && len2 ? 2 : (len1 || len2 ? 1 : 0);
I think this is the same as

		if (len1)
			extent_cnt_delta++;
		if (len2)
			extent_cnt_delta++;
		extent_cnt_delta--;



> +                extent_cnt_delta -= 1;
> +                if (ct3d->dc.total_extent_count + extent_cnt_delta >
> +                    CXL_NUM_EXTENTS_SUPPORTED) {

This early overflow detect seems valid to me because a device might run
out or resource mid processing the list even if it would fit at the end.
Good.
> +                    ret = CXL_MBOX_RESOURCES_EXHAUSTED;
> +                    goto free_and_exit;
> +                }
> +
> +                offset = (ent->start_dpa - region->base) / region->block_size;
> +                nbits = ent->len / region->block_size;
> +                bitmap_clear(bitmaps_copied[rid], offset, nbits);
> +                cxl_remove_extent_from_extent_list(&tmp_list, ent);
> +
> +                 if (len1) {
> +                    offset = (dpa - region->base) / region->block_size;
> +                    nbits = len1 / region->block_size;
> +                    bitmap_set(bitmaps_copied[rid], offset, nbits);
> +                    cxl_insert_extent_to_extent_list(&tmp_list,
> +                                                     ent_start_dpa, len1,
> +                                                     NULL, 0);
> +                 }
> +
> +                 if (len2) {
> +                    offset = (dpa + len - region->base) / region->block_size;
> +                    nbits = len2 / region->block_size;
> +                    bitmap_set(bitmaps_copied[rid], offset, nbits);
> +                    cxl_insert_extent_to_extent_list(&tmp_list, dpa + len,
> +                                                     len2, NULL, 0);
> +                 }
> +                 break;
> +             }
> +         }
> +    }
> +
> +free_and_exit:
> +    for (i = 0; i < ct3d->dc.num_regions; i++) {
> +        g_free(bitmaps_copied[i]);
> +    }
> +    g_free(bitmaps_copied);
> +
> +    while (!QTAILQ_EMPTY(&tmp_list)) {
> +        ent = QTAILQ_FIRST(&tmp_list);
> +        cxl_remove_extent_from_extent_list(&tmp_list, ent);
> +    }
> +
> +    return ret;
> +}
> +
>  /*
>   * CXL r3.1 section 8.2.9.9.9.4: Release Dynamic Capacity (Opcode 4803h)
>   */
> @@ -1644,15 +1793,28 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>          return ret;
>      }
>  
> -    for (i = 0; i < in->num_entries_updated; i++) {
> -        bool found = false;
> +    ret = cxl_detect_extent_overflow(ct3d, in);
> +    if (ret != CXL_MBOX_SUCCESS) {
> +        return ret;
> +    }
>  
> +    /*
> +     * After this point, it is guaranteed that the extents in the
> +     * updated extent list to release is valid, that means:
> +     * 1. All extents in the list have no overlaps;
> +     * 2. Each extent belongs to a valid DC region;
> +     * 3. The DPA range of each extent is covered by valid extent
> +     * in the device.
> +     */
> +    for (i = 0; i < in->num_entries_updated; i++) {
>          dpa = in->updated_entries[i].start_dpa;
>          len = in->updated_entries[i].len;
>  
> +process_leftover:
>          QTAILQ_FOREACH(ent, extent_list, node) {
>              /* Found the extent overlapping with */
>              if (ent->start_dpa <= dpa && dpa < ent->start_dpa + ent->len) {
> +                /* Case 1: The to-release extent is subset of ent */
>                  if (dpa + len <= ent->start_dpa + ent->len) {
>                      /*
>                       * The incoming extent covers a portion of an extent
> @@ -1669,17 +1831,6 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>                      uint64_t len1 = dpa - ent_start_dpa;
>                      uint64_t len2 = ent_start_dpa + ent_len - dpa - len;
>  
> -                    /*
> -                     * TODO: checking for possible extent overflow, will be
> -                     * moved into a dedicated function of detecting extent
> -                     * overflow.
> -                     */
> -                    if (len1 && len2 && ct3d->dc.total_extent_count ==
> -                        CXL_NUM_EXTENTS_SUPPORTED) {
> -                        return CXL_MBOX_RESOURCES_EXHAUSTED;
> -                    }
> -
> -                    found = true;
>                      cxl_remove_extent_from_extent_list(extent_list, ent);
>                      ct3d->dc.total_extent_count -= 1;
>                      ct3_clear_region_block_backed(ct3d, ent_start_dpa, ent_len);
> @@ -1700,20 +1851,34 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>                      break;
>                  } else {
>                      /*
> -                     * TODO: we reject the attempt to remove an extent that
> -                     * overlaps with multiple extents in the device for now,
> -                     * once the bitmap indicating whether a DPA range is
> -                     * covered by valid extents is introduced, will allow it.
> +                     * Case 2: the to-release extent overlaps with multiple
> +                     * extents, including the superset case
>                       */
> -                    return CXL_MBOX_INVALID_PA;
> +                    uint64_t ent_start_dpa = ent->start_dpa;
> +                    uint64_t ent_len = ent->len;
> +                    uint64_t len1 = dpa - ent_start_dpa;
> +
> +                    cxl_remove_extent_from_extent_list(extent_list, ent);
> +                    ct3d->dc.total_extent_count -= 1;
> +                    ct3_clear_region_block_backed(ct3d, ent_start_dpa, ent_len);
> +
> +                    if (len1) {
> +                        cxl_insert_extent_to_extent_list(extent_list,
> +                                                         ent_start_dpa, len1,
> +                                                         NULL, 0);
> +                        ct3d->dc.total_extent_count += 1;
> +                        ct3_set_region_block_backed(ct3d, ent_start_dpa, len1);
> +                    }
> +                    /*
> +                     * processing the portion of the range following current
> +                     * extent

> +                     */
> +                    len = dpa + len - ent_start_dpa - ent_len;
> +                    dpa = ent_start_dpa + ent_len;
> +                    goto process_leftover;

I'd slightly prefer a while loop I think based on len > 0
It does add indent, but easier to follow for me than a retry type goto.


>                  }
>              }
>          }
> -
> -        if (!found) {
> -            /* Try to remove a non-existing extent. */
> -            return CXL_MBOX_INVALID_PA;
> -        }
>      }
>  
>      return CXL_MBOX_SUCCESS;


WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via <qemu-devel@nongnu.org>
To: <nifan.cxl@gmail.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
	<gregory.price@memverge.com>, <ira.weiny@intel.com>,
	<dan.j.williams@intel.com>, <a.manzanares@samsung.com>,
	<dave@stgolabs.net>, <nmtadam.samsung@gmail.com>,
	<jim.harris@samsung.com>, <Jorgen.Hansen@wdc.com>,
	<wj28.lee@gmail.com>, Fan Ni <fan.ni@samsung.com>
Subject: Re: [PATCH v5 11/13] hw/cxl/cxl-mailbox-utils: Add partial and superset extent release mailbox support
Date: Wed, 6 Mar 2024 18:09:46 +0000	[thread overview]
Message-ID: <20240306180946.00005161@Huawei.com> (raw)
In-Reply-To: <20240304194331.1586191-12-nifan.cxl@gmail.com>

On Mon,  4 Mar 2024 11:34:06 -0800
nifan.cxl@gmail.com wrote:

> From: Fan Ni <fan.ni@samsung.com>
> 
> With the change, we extend the extent release mailbox command processing
> to allow more flexible release. As long as the DPA range of the extent to
> release is covered by valid extent(s) in the device, the release can be
> performed.
> 
> Signed-off-by: Fan Ni <fan.ni@samsung.com>

Ouch this is more complex than I was thinking, but seems correct to me.

A few minor comments inline

Jonathan

> +/*
> + * Detect potential extent overflow caused by extent split during processing
> + * extent release requests, also allow releasing superset of extents where the
> + * extent to release covers the range of multiple extents in the device.
> + * Note:
> + * 1.we will reject releasing an extent if some portion of its rang is

range

> + * not covered by valid extents.
> + * 2.This function is called after cxl_detect_malformed_extent_list so checks
> + * already performed there will be skipped.
> + */
> +static CXLRetCode cxl_detect_extent_overflow(const CXLType3Dev *ct3d,
> +        const CXLUpdateDCExtentListInPl *in)

This code is basically dry running the actual removal.  Can we just
make the core code the same for both cases?  The bit where you update bitmaps
and extent lists at least.

> +{
> +    uint64_t nbits, offset;
> +    const CXLDCRegion *region;
> +    unsigned long **bitmaps_copied;
> +    uint64_t dpa, len;
> +    int i, rid;
> +    CXLRetCode ret = CXL_MBOX_SUCCESS;
> +    long extent_cnt_delta = 0;
> +    CXLDCExtentList tmp_list;
> +    CXLDCExtent *ent;
> +
> +    QTAILQ_INIT(&tmp_list);
> +    copy_extent_list(&tmp_list, &ct3d->dc.extents);
> +
> +    bitmaps_copied = g_new0(unsigned long *, ct3d->dc.num_regions);
> +    for (i = 0; i < ct3d->dc.num_regions; i++) {
> +        region = &ct3d->dc.regions[i];
> +        nbits = region->len / region->block_size;
> +        bitmaps_copied[i] = bitmap_new(nbits);
> +        bitmap_copy(bitmaps_copied[i], region->blk_bitmap, nbits);
> +    }
> +
> +    for (i = 0; i < in->num_entries_updated; i++) {
> +        dpa = in->updated_entries[i].start_dpa;
> +        len = in->updated_entries[i].len;
> +
> +        rid = cxl_find_dc_region_id(ct3d, dpa, len);
> +        region = &ct3d->dc.regions[rid];
> +        offset = (dpa - region->base) / region->block_size;
> +        nbits = len / region->block_size;
> +
> +        /* Check whether range [dpa, dpa + len) is covered by valid range */
> +        if (find_next_zero_bit(bitmaps_copied[rid], offset + nbits, offset) <
> +                               offset + nbits) {
> +            ret = CXL_MBOX_INVALID_PA;
> +            goto free_and_exit;
> +        }
> +
> +        QTAILQ_FOREACH(ent, &tmp_list, node) {
> +            /* Only split within an extent can cause extent count increase */
> +            if (ent->start_dpa <= dpa &&
> +                dpa + len <= ent->start_dpa + ent->len) {
> +                uint64_t ent_start_dpa = ent->start_dpa;
> +                uint64_t ent_len = ent->len;
> +                uint64_t len1 = dpa - ent_start_dpa;
> +                uint64_t len2 = ent_start_dpa + ent_len - dpa - len;
> +
> +                extent_cnt_delta += len1 && len2 ? 2 : (len1 || len2 ? 1 : 0);
I think this is the same as

		if (len1)
			extent_cnt_delta++;
		if (len2)
			extent_cnt_delta++;
		extent_cnt_delta--;



> +                extent_cnt_delta -= 1;
> +                if (ct3d->dc.total_extent_count + extent_cnt_delta >
> +                    CXL_NUM_EXTENTS_SUPPORTED) {

This early overflow detect seems valid to me because a device might run
out or resource mid processing the list even if it would fit at the end.
Good.
> +                    ret = CXL_MBOX_RESOURCES_EXHAUSTED;
> +                    goto free_and_exit;
> +                }
> +
> +                offset = (ent->start_dpa - region->base) / region->block_size;
> +                nbits = ent->len / region->block_size;
> +                bitmap_clear(bitmaps_copied[rid], offset, nbits);
> +                cxl_remove_extent_from_extent_list(&tmp_list, ent);
> +
> +                 if (len1) {
> +                    offset = (dpa - region->base) / region->block_size;
> +                    nbits = len1 / region->block_size;
> +                    bitmap_set(bitmaps_copied[rid], offset, nbits);
> +                    cxl_insert_extent_to_extent_list(&tmp_list,
> +                                                     ent_start_dpa, len1,
> +                                                     NULL, 0);
> +                 }
> +
> +                 if (len2) {
> +                    offset = (dpa + len - region->base) / region->block_size;
> +                    nbits = len2 / region->block_size;
> +                    bitmap_set(bitmaps_copied[rid], offset, nbits);
> +                    cxl_insert_extent_to_extent_list(&tmp_list, dpa + len,
> +                                                     len2, NULL, 0);
> +                 }
> +                 break;
> +             }
> +         }
> +    }
> +
> +free_and_exit:
> +    for (i = 0; i < ct3d->dc.num_regions; i++) {
> +        g_free(bitmaps_copied[i]);
> +    }
> +    g_free(bitmaps_copied);
> +
> +    while (!QTAILQ_EMPTY(&tmp_list)) {
> +        ent = QTAILQ_FIRST(&tmp_list);
> +        cxl_remove_extent_from_extent_list(&tmp_list, ent);
> +    }
> +
> +    return ret;
> +}
> +
>  /*
>   * CXL r3.1 section 8.2.9.9.9.4: Release Dynamic Capacity (Opcode 4803h)
>   */
> @@ -1644,15 +1793,28 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>          return ret;
>      }
>  
> -    for (i = 0; i < in->num_entries_updated; i++) {
> -        bool found = false;
> +    ret = cxl_detect_extent_overflow(ct3d, in);
> +    if (ret != CXL_MBOX_SUCCESS) {
> +        return ret;
> +    }
>  
> +    /*
> +     * After this point, it is guaranteed that the extents in the
> +     * updated extent list to release is valid, that means:
> +     * 1. All extents in the list have no overlaps;
> +     * 2. Each extent belongs to a valid DC region;
> +     * 3. The DPA range of each extent is covered by valid extent
> +     * in the device.
> +     */
> +    for (i = 0; i < in->num_entries_updated; i++) {
>          dpa = in->updated_entries[i].start_dpa;
>          len = in->updated_entries[i].len;
>  
> +process_leftover:
>          QTAILQ_FOREACH(ent, extent_list, node) {
>              /* Found the extent overlapping with */
>              if (ent->start_dpa <= dpa && dpa < ent->start_dpa + ent->len) {
> +                /* Case 1: The to-release extent is subset of ent */
>                  if (dpa + len <= ent->start_dpa + ent->len) {
>                      /*
>                       * The incoming extent covers a portion of an extent
> @@ -1669,17 +1831,6 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>                      uint64_t len1 = dpa - ent_start_dpa;
>                      uint64_t len2 = ent_start_dpa + ent_len - dpa - len;
>  
> -                    /*
> -                     * TODO: checking for possible extent overflow, will be
> -                     * moved into a dedicated function of detecting extent
> -                     * overflow.
> -                     */
> -                    if (len1 && len2 && ct3d->dc.total_extent_count ==
> -                        CXL_NUM_EXTENTS_SUPPORTED) {
> -                        return CXL_MBOX_RESOURCES_EXHAUSTED;
> -                    }
> -
> -                    found = true;
>                      cxl_remove_extent_from_extent_list(extent_list, ent);
>                      ct3d->dc.total_extent_count -= 1;
>                      ct3_clear_region_block_backed(ct3d, ent_start_dpa, ent_len);
> @@ -1700,20 +1851,34 @@ static CXLRetCode cmd_dcd_release_dyn_cap(const struct cxl_cmd *cmd,
>                      break;
>                  } else {
>                      /*
> -                     * TODO: we reject the attempt to remove an extent that
> -                     * overlaps with multiple extents in the device for now,
> -                     * once the bitmap indicating whether a DPA range is
> -                     * covered by valid extents is introduced, will allow it.
> +                     * Case 2: the to-release extent overlaps with multiple
> +                     * extents, including the superset case
>                       */
> -                    return CXL_MBOX_INVALID_PA;
> +                    uint64_t ent_start_dpa = ent->start_dpa;
> +                    uint64_t ent_len = ent->len;
> +                    uint64_t len1 = dpa - ent_start_dpa;
> +
> +                    cxl_remove_extent_from_extent_list(extent_list, ent);
> +                    ct3d->dc.total_extent_count -= 1;
> +                    ct3_clear_region_block_backed(ct3d, ent_start_dpa, ent_len);
> +
> +                    if (len1) {
> +                        cxl_insert_extent_to_extent_list(extent_list,
> +                                                         ent_start_dpa, len1,
> +                                                         NULL, 0);
> +                        ct3d->dc.total_extent_count += 1;
> +                        ct3_set_region_block_backed(ct3d, ent_start_dpa, len1);
> +                    }
> +                    /*
> +                     * processing the portion of the range following current
> +                     * extent

> +                     */
> +                    len = dpa + len - ent_start_dpa - ent_len;
> +                    dpa = ent_start_dpa + ent_len;
> +                    goto process_leftover;

I'd slightly prefer a while loop I think based on len > 0
It does add indent, but easier to follow for me than a retry type goto.


>                  }
>              }
>          }
> -
> -        if (!found) {
> -            /* Try to remove a non-existing extent. */
> -            return CXL_MBOX_INVALID_PA;
> -        }
>      }
>  
>      return CXL_MBOX_SUCCESS;



  reply	other threads:[~2024-03-06 18:09 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-04 19:33 [PATCH v5 00/13] Enabling DCD emulation support in Qemu nifan.cxl
2024-03-04 19:33 ` [PATCH v5 01/13] hw/cxl/cxl-mailbox-utils: Add dc_event_log_size field to output payload of identify memory device command nifan.cxl
2024-03-06 15:07   ` Jonathan Cameron
2024-03-06 15:07     ` Jonathan Cameron via
2024-03-04 19:33 ` [PATCH v5 02/13] hw/cxl/cxl-mailbox-utils: Add dynamic capacity region representative and mailbox command support nifan.cxl
2024-03-06 15:24   ` Jonathan Cameron
2024-03-06 15:24     ` Jonathan Cameron via
2024-03-04 19:33 ` [PATCH v5 03/13] include/hw/cxl/cxl_device: Rename mem_size as static_mem_size for type3 memory devices nifan.cxl
2024-03-06 15:39   ` Jonathan Cameron
2024-03-06 15:39     ` Jonathan Cameron via
2024-03-04 19:33 ` [PATCH v5 04/13] hw/mem/cxl_type3: Add support to create DC regions to " nifan.cxl
2024-03-06 15:48   ` Jonathan Cameron
2024-03-06 15:48     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 05/13] hw/mem/cxl-type3: Refactor ct3_build_cdat_entries_for_mr to take mr size insead of mr as argument nifan.cxl
2024-03-06 16:02   ` Jonathan Cameron
2024-03-06 16:02     ` Jonathan Cameron via
2024-03-06 16:03   ` Jonathan Cameron
2024-03-06 16:03     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 06/13] hw/mem/cxl_type3: Add host backend and address space handling for DC regions nifan.cxl
2024-03-06 16:28   ` Jonathan Cameron
2024-03-06 16:28     ` Jonathan Cameron via
2024-03-06 19:14     ` fan
2024-03-07 12:16       ` Jonathan Cameron
2024-03-07 12:16         ` Jonathan Cameron via
2024-03-07 23:34         ` fan
2024-03-14 20:43     ` fan
2024-03-04 19:34 ` [PATCH v5 07/13] hw/mem/cxl_type3: Add DC extent list representative and get DC extent list mailbox support nifan.cxl
2024-03-06 16:37   ` Jonathan Cameron
2024-03-06 16:37     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 08/13] hw/cxl/cxl-mailbox-utils: Add mailbox commands to support add/release dynamic capacity response nifan.cxl
2024-03-06 17:28   ` Jonathan Cameron
2024-03-06 17:28     ` Jonathan Cameron via
2024-03-06 21:39     ` fan
2024-03-07 12:20       ` Jonathan Cameron
2024-03-07 12:20         ` Jonathan Cameron via
2024-03-06 22:34     ` fan
2024-03-07 12:30       ` Jonathan Cameron
2024-03-07 12:30         ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 09/13] hw/cxl/events: Add qmp interfaces to add/release dynamic capacity extents nifan.cxl
2024-03-06 17:48   ` Jonathan Cameron
2024-03-06 17:48     ` Jonathan Cameron via
2024-03-06 23:15     ` fan
2024-03-07 12:45       ` Jonathan Cameron
2024-03-07 12:45         ` Jonathan Cameron via
2024-03-09  4:35         ` fan
2024-03-12 12:37           ` Jonathan Cameron
2024-03-12 12:37             ` Jonathan Cameron via
2024-03-12 16:27             ` fan
2024-03-06 23:36     ` fan
2024-03-07 12:47       ` Jonathan Cameron
2024-03-07 12:47         ` Jonathan Cameron via
2024-04-24 13:09   ` Markus Armbruster
2024-04-24 17:10     ` fan
2024-04-24 17:26       ` Markus Armbruster
2024-04-24 17:44         ` fan
2024-04-24 17:33     ` Ira Weiny
2024-04-26 15:55       ` Jonathan Cameron
2024-04-26 15:55         ` Jonathan Cameron via
2024-04-26 16:22         ` Gregory Price
2024-04-24 17:39     ` fan
2024-04-25  5:48       ` Markus Armbruster
2024-04-25 17:30         ` Ira Weiny
2024-04-26 16:00           ` Jonathan Cameron
2024-04-26 16:00             ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 10/13] hw/mem/cxl_type3: Add dpa range validation for accesses to DC regions nifan.cxl
2024-03-06 17:50   ` Jonathan Cameron
2024-03-06 17:50     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 11/13] hw/cxl/cxl-mailbox-utils: Add partial and superset extent release mailbox support nifan.cxl
2024-03-06 18:09   ` Jonathan Cameron [this message]
2024-03-06 18:09     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 12/13] hw/mem/cxl_type3: Allow to release partial extent and extent superset in QMP interface nifan.cxl
2024-03-06 18:14   ` Jonathan Cameron
2024-03-06 18:14     ` Jonathan Cameron via
2024-03-04 19:34 ` [PATCH v5 13/13] qapi/cxl.json: Add QMP interfaces to print out accepted and pending DC extents nifan.cxl
2024-03-05 16:09   ` Jonathan Cameron
2024-03-05 16:09     ` Jonathan Cameron via
2024-03-05 16:15     ` Daniel P. Berrangé
2024-03-05 17:09       ` fan
2024-03-05 17:14         ` Daniel P. Berrangé
2024-04-24 13:12           ` Markus Armbruster
2024-04-24 17:12             ` fan

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=20240306180946.00005161@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=Jorgen.Hansen@wdc.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=gregory.price@memverge.com \
    --cc=ira.weiny@intel.com \
    --cc=jim.harris@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nifan.cxl@gmail.com \
    --cc=nmtadam.samsung@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wj28.lee@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.