[{"id":3669786,"web_url":"http://patchwork.ozlabs.org/comment/3669786/","msgid":"<87mrzuei5f.fsf@pond.sub.org>","list_archive_url":null,"date":"2026-03-26T15:15:40","subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","submitter":{"id":2645,"url":"http://patchwork.ozlabs.org/api/people/2645/","name":"Markus Armbruster","email":"armbru@redhat.com"},"content":"I'm a near-complete CXL ignoramus, and beg your patience.\n\nAlireza Sanaee <alireza.sanaee@huawei.com> writes:\n\n> Add a small status query so orchestration layers can check whether a tagged\n> extent is still pending, committed, or no longer present after a release\n> request.\n\nWhy would they want to check?\n\nWhat is a \"release request\"?\n\n>\n> Introduce the ExtentStatus QAPI struct and the\n> cxl-release-dynamic-capacity-status command.\n>\n> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>\n\n[...]\n\n> diff --git a/qapi/cxl.json b/qapi/cxl.json\n> index 81d6198ba0..53325ba530 100644\n> --- a/qapi/cxl.json\n> +++ b/qapi/cxl.json\n> @@ -636,3 +636,49 @@\n>             },\n>    'features': [ 'unstable' ]\n>  }\n> +\n> +##\n> +# @ExtentStatus:\n\nBlank line here, please.\n\n> +# This is an object that describes the status of an extent.\n> +#\n> +# @status:   String indicating the overall result, e.g. \"success\".\n\nWhat are the possible values?  Are they defined in some spec?\n\n> +# @message:  Human-readable description of the outcome.\n\nIntended use?\n\n> +#\n> +# Since: 9.1\n\n11.1 most likely.\n\n> +##\n> +{ 'struct': 'ExtentStatus',\n> +      'data': { 'status': 'str', 'message': 'str' }\n> +}\n> +\n> +##\n> +# @cxl-release-dynamic-capacity-status:\n> +#\n> +# This commands checks if an extent tag has been released or not.\n\nUse imperative mood to describe commands: \"Check whether an extent tag\nhas been released.\"\n\n> +#\n> +# @path: path to the CXL Dynamic Capacity Device in the QOM tree.\n\nWe commonly call such members @qom-path.\n\n> +#\n> +# @host-id: The \"Host ID\" field as defined in Compute Express Link\n> +#     (CXL) Specification, Revision 3.1, Table 7-71.\n> +#\n> +# @region: The \"Region Number\" field as defined in Compute Express\n> +#     Link Specification, Revision 3.1, Table 7-71.  Valid range\n> +#     is from 0-7.\n> +#\n> +# @tag: The \"Tag\" field as defined in Compute Express Link (CXL)\n> +#     Specification, Revision 3.1, Table 7-71.\n\nI guess the command interrogates something called \"extent\", and the\nsomething is related to the CXL device at @path in the QOM tree.\nCorrect?\n\nHow is it related?  Is it a part of the device?\n\nI further guess multiple extends can be so related, and @host-id,\n@region, and @tag identify select the one we want to interrogate.\nCorrect?\n\n> +#\n> +# Features:\n> +#\n> +# @unstable: For now this command is subject to change.\n\nThe conventional language is \"This command is experimental.\"\n\n> +#\n> +# Since: 9.1\n\n11.1 most likely.\n\n> +##\n> +{ 'command': 'cxl-release-dynamic-capacity-status',\n> +  'data': { 'path': 'str',\n> +            'host-id': 'uint16',\n> +            'region': 'uint8',\n> +            'tag': 'str'\n> +          },\n> +  'features': [ 'unstable' ],\n> +  'returns': 'ExtentStatus'\n\nSwap these two lines, please.\n\n> +}","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (1024-bit key;\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=BVG7UkoO;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)"],"Received":["from lists.gnu.org (lists.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fhS5x5nqbz1yGD\n\tfor <incoming@patchwork.ozlabs.org>; Fri, 27 Mar 2026 02:16:05 +1100 (AEDT)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from <qemu-devel-bounces@nongnu.org>)\n\tid 1w5mRB-00077r-6O; Thu, 26 Mar 2026 11:15:57 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w5mR9-00076N-BF\n for qemu-devel@nongnu.org; Thu, 26 Mar 2026 11:15:55 -0400","from us-smtp-delivery-124.mimecast.com ([170.10.133.124])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w5mR7-0003sR-8J\n for qemu-devel@nongnu.org; Thu, 26 Mar 2026 11:15:55 -0400","from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com\n (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by\n relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-348-dVAnXoqzMDWhQysiOPlhcw-1; Thu,\n 26 Mar 2026 11:15:46 -0400","from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com\n (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS\n id EEABB1956048; Thu, 26 Mar 2026 15:15:43 +0000 (UTC)","from blackfin.pond.sub.org (unknown [10.45.242.6])\n by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with\n ESMTPS\n id 085F31955D84; Thu, 26 Mar 2026 15:15:42 +0000 (UTC)","by blackfin.pond.sub.org (Postfix, from userid 1000)\n id 952BA21E6937; Thu, 26 Mar 2026 16:15:40 +0100 (CET)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1774538150;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n in-reply-to:in-reply-to:references:references;\n bh=vzpehDqYgCyCogpznJ1yRYvkvpNP6+3YYzUqRgqyluU=;\n b=BVG7UkoO6VgQlef+ucU1Jj5cgtahZ1BD9LLXxYZBsLlTvZFF4nvfskYBqlB0K9SJQTGY4N\n P+LzV44wIT95tTsMeZ9nfCORL5nJn0QNhAR2ezAUjuk7tZwJMKRzkXFEcMt4AYUlYy2R3s\n A4Dy2e+4BY/p4ev7GywY2hlPHoheMaM=","X-MC-Unique":"dVAnXoqzMDWhQysiOPlhcw-1","X-Mimecast-MFC-AGG-ID":"dVAnXoqzMDWhQysiOPlhcw_1774538145","From":"Markus Armbruster <armbru@redhat.com>","To":"Alireza Sanaee <alireza.sanaee@huawei.com>","Cc":"<qemu-devel@nongnu.org>,  <anisa.su@samsung.com>,\n <berrange@redhat.com>,  <eblake@redhat.com>,\n <jonathan.cameron@huawei.com>,  <linux-cxl@vger.kernel.org>,\n <linuxarm@huawei.com>,  <lizhijian@fujitsu.com>,  <mst@redhat.com>,\n <pbonzini@redhat.com>,  <gourry@gourry.net>,  <nifan.cxl@gmail.com>,\n <me@linux.beauty>","Subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","In-Reply-To":"<20260325184259.366-10-alireza.sanaee@huawei.com> (Alireza\n Sanaee's message of \"Wed, 25 Mar 2026 18:42:57 +0000\")","References":"<20260325184259.366-1-alireza.sanaee@huawei.com>\n <20260325184259.366-10-alireza.sanaee@huawei.com>","Date":"Thu, 26 Mar 2026 16:15:40 +0100","Message-ID":"<87mrzuei5f.fsf@pond.sub.org>","User-Agent":"Gnus/5.13 (Gnus v5.13)","MIME-Version":"1.0","Content-Type":"text/plain","X-Scanned-By":"MIMEDefang 3.0 on 10.30.177.17","Received-SPF":"pass client-ip=170.10.133.124; envelope-from=armbru@redhat.com;\n helo=us-smtp-delivery-124.mimecast.com","X-Spam_score_int":"-20","X-Spam_score":"-2.1","X-Spam_bar":"--","X-Spam_report":"(-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001,\n DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,\n RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001,\n RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,\n SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development <qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<https://lists.nongnu.org/archive/html/qemu-devel>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}},{"id":3670398,"web_url":"http://patchwork.ozlabs.org/comment/3670398/","msgid":"<20260327151811.00005564.alireza.sanaee@huawei.com>","list_archive_url":null,"date":"2026-03-27T15:18:11","subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","submitter":{"id":90159,"url":"http://patchwork.ozlabs.org/api/people/90159/","name":"Alireza Sanaee","email":"alireza.sanaee@huawei.com"},"content":"On Thu, 26 Mar 2026 16:15:40 +0100\nMarkus Armbruster <armbru@redhat.com> wrote:\n\nHi Markus,\n\nThis commit adds a test command to check whether an extent (a piece of memory region) has been released or not by the guest.\nThe process of removal is highly asynchronous, that's why I needed to add a new command to check it.\n\nI would be happy to drop this patch, as this is extra.\n\nThanks,\nAli\n\n> I'm a near-complete CXL ignoramus, and beg your patience.\n> \n> Alireza Sanaee <alireza.sanaee@huawei.com> writes:\n> \n> > Add a small status query so orchestration layers can check whether a tagged\n> > extent is still pending, committed, or no longer present after a release\n> > request.  \n> \n> Why would they want to check?\n> \n> What is a \"release request\"?\n> \n> >\n> > Introduce the ExtentStatus QAPI struct and the\n> > cxl-release-dynamic-capacity-status command.\n> >\n> > Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>  \n> \n> [...]\n> \n> > diff --git a/qapi/cxl.json b/qapi/cxl.json\n> > index 81d6198ba0..53325ba530 100644\n> > --- a/qapi/cxl.json\n> > +++ b/qapi/cxl.json\n> > @@ -636,3 +636,49 @@\n> >             },\n> >    'features': [ 'unstable' ]\n> >  }\n> > +\n> > +##\n> > +# @ExtentStatus:  \n> \n> Blank line here, please.\n> \n> > +# This is an object that describes the status of an extent.\n> > +#\n> > +# @status:   String indicating the overall result, e.g. \"success\".  \n> \n> What are the possible values?  Are they defined in some spec?\n> \n> > +# @message:  Human-readable description of the outcome.  \n> \n> Intended use?\n> \n> > +#\n> > +# Since: 9.1  \n> \n> 11.1 most likely.\n> \n> > +##\n> > +{ 'struct': 'ExtentStatus',\n> > +      'data': { 'status': 'str', 'message': 'str' }\n> > +}\n> > +\n> > +##\n> > +# @cxl-release-dynamic-capacity-status:\n> > +#\n> > +# This commands checks if an extent tag has been released or not.  \n> \n> Use imperative mood to describe commands: \"Check whether an extent tag\n> has been released.\"\n> \n> > +#\n> > +# @path: path to the CXL Dynamic Capacity Device in the QOM tree.  \n> \n> We commonly call such members @qom-path.\n> \n> > +#\n> > +# @host-id: The \"Host ID\" field as defined in Compute Express Link\n> > +#     (CXL) Specification, Revision 3.1, Table 7-71.\n> > +#\n> > +# @region: The \"Region Number\" field as defined in Compute Express\n> > +#     Link Specification, Revision 3.1, Table 7-71.  Valid range\n> > +#     is from 0-7.\n> > +#\n> > +# @tag: The \"Tag\" field as defined in Compute Express Link (CXL)\n> > +#     Specification, Revision 3.1, Table 7-71.  \n> \n> I guess the command interrogates something called \"extent\", and the\n> something is related to the CXL device at @path in the QOM tree.\n> Correct?\n> \n> How is it related?  Is it a part of the device?\n> \n> I further guess multiple extends can be so related, and @host-id,\n> @region, and @tag identify select the one we want to interrogate.\n> Correct?\n> \n> > +#\n> > +# Features:\n> > +#\n> > +# @unstable: For now this command is subject to change.  \n> \n> The conventional language is \"This command is experimental.\"\n> \n> > +#\n> > +# Since: 9.1  \n> \n> 11.1 most likely.\n> \n> > +##\n> > +{ 'command': 'cxl-release-dynamic-capacity-status',\n> > +  'data': { 'path': 'str',\n> > +            'host-id': 'uint16',\n> > +            'region': 'uint8',\n> > +            'tag': 'str'\n> > +          },\n> > +  'features': [ 'unstable' ],\n> > +  'returns': 'ExtentStatus'  \n> \n> Swap these two lines, please.\n> \n> > +}  \n> \n>","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":"legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)","Received":["from lists.gnu.org (lists.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fj46m2cGQz1y1P\n\tfor <incoming@patchwork.ozlabs.org>; Sat, 28 Mar 2026 02:18:56 +1100 (AEDT)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from <qemu-devel-bounces@nongnu.org>)\n\tid 1w68xP-0003PD-7U; Fri, 27 Mar 2026 11:18:44 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <alireza.sanaee@huawei.com>)\n id 1w68xK-0003Ov-0W\n for qemu-devel@nongnu.org; Fri, 27 Mar 2026 11:18:38 -0400","from frasgout.his.huawei.com ([185.176.79.56])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <alireza.sanaee@huawei.com>)\n id 1w68xH-00055W-9X\n for qemu-devel@nongnu.org; Fri, 27 Mar 2026 11:18:37 -0400","from mail.maildlp.com (unknown [172.18.224.83])\n by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4fj45p1HzJzJ46Bp;\n Fri, 27 Mar 2026 23:18:06 +0800 (CST)","from dubpeml500005.china.huawei.com (unknown [7.214.145.207])\n by mail.maildlp.com (Postfix) with ESMTPS id 30FA640577;\n Fri, 27 Mar 2026 23:18:18 +0800 (CST)","from localhost (10.203.177.99) by dubpeml500005.china.huawei.com\n (7.214.145.207) with Microsoft SMTP Server (version=TLS1_2,\n cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Fri, 27 Mar\n 2026 15:18:17 +0000"],"Date":"Fri, 27 Mar 2026 15:18:11 +0000","To":"Markus Armbruster <armbru@redhat.com>","CC":"<qemu-devel@nongnu.org>, <anisa.su@samsung.com>, <berrange@redhat.com>,\n <eblake@redhat.com>, <jonathan.cameron@huawei.com>,\n <linux-cxl@vger.kernel.org>, <linuxarm@huawei.com>, <lizhijian@fujitsu.com>,\n <mst@redhat.com>, <pbonzini@redhat.com>, <gourry@gourry.net>,\n <nifan.cxl@gmail.com>, <me@linux.beauty>","Subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","Message-ID":"<20260327151811.00005564.alireza.sanaee@huawei.com>","In-Reply-To":"<87mrzuei5f.fsf@pond.sub.org>","References":"<20260325184259.366-1-alireza.sanaee@huawei.com>\n <20260325184259.366-10-alireza.sanaee@huawei.com>\n <87mrzuei5f.fsf@pond.sub.org>","Organization":"Huawei","X-Mailer":"Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32)","MIME-Version":"1.0","Content-Type":"text/plain; charset=\"US-ASCII\"","Content-Transfer-Encoding":"7bit","X-Originating-IP":"[10.203.177.99]","X-ClientProxiedBy":"lhrpeml500009.china.huawei.com (7.191.174.84) To\n dubpeml500005.china.huawei.com (7.214.145.207)","Received-SPF":"pass client-ip=185.176.79.56;\n envelope-from=alireza.sanaee@huawei.com; helo=frasgout.his.huawei.com","X-Spam_score_int":"-41","X-Spam_score":"-4.2","X-Spam_bar":"----","X-Spam_report":"(-4.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,\n RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001,\n RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,\n SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development <qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<https://lists.nongnu.org/archive/html/qemu-devel>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Reply-to":"Alireza Sanaee <alireza.sanaee@huawei.com>","From":"Alireza Sanaee via qemu development <qemu-devel@nongnu.org>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}},{"id":3670635,"web_url":"http://patchwork.ozlabs.org/comment/3670635/","msgid":"<87zf3s1ohc.fsf@pond.sub.org>","list_archive_url":null,"date":"2026-03-28T06:01:51","subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","submitter":{"id":2645,"url":"http://patchwork.ozlabs.org/api/people/2645/","name":"Markus Armbruster","email":"armbru@redhat.com"},"content":"Alireza Sanaee <alireza.sanaee@huawei.com> writes:\n\n> On Thu, 26 Mar 2026 16:15:40 +0100\n> Markus Armbruster <armbru@redhat.com> wrote:\n>\n> Hi Markus,\n>\n> This commit adds a test command to check whether an extent (a piece of memory region) has been released or not by the guest.\n> The process of removal is highly asynchronous, that's why I needed to add a new command to check it.\n>\n> I would be happy to drop this patch, as this is extra.\n\nSo your motivation for adding the command is \"just\" testing.  Correct?\n\nCan you think of other uses?\n\nIn particular, would a management application need this query to monitor\nremoval?\n\nThe description of feature @unstable may need to be adjusted for the\nanswers we work out here.\n\n>\n> Thanks,\n> Ali","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (1024-bit key;\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=ZuDggVp9;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)"],"Received":["from lists.gnu.org (lists.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fjRkw29bvz1y1j\n\tfor <incoming@patchwork.ozlabs.org>; Sat, 28 Mar 2026 17:03:02 +1100 (AEDT)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from <qemu-devel-bounces@nongnu.org>)\n\tid 1w6MkK-0000BL-3h; Sat, 28 Mar 2026 02:02:08 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w6MkI-0000BB-SL\n for qemu-devel@nongnu.org; Sat, 28 Mar 2026 02:02:06 -0400","from us-smtp-delivery-124.mimecast.com ([170.10.129.124])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w6MkH-0002IH-Ay\n for qemu-devel@nongnu.org; Sat, 28 Mar 2026 02:02:06 -0400","from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com\n (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by\n relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-461-QK3TLCZJNl6B8duKTuTrnw-1; Sat,\n 28 Mar 2026 02:01:56 -0400","from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com\n (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS\n id AA6AC19560BB; Sat, 28 Mar 2026 06:01:54 +0000 (UTC)","from blackfin.pond.sub.org (unknown [10.45.242.6])\n by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with\n ESMTPS\n id 803171955D84; Sat, 28 Mar 2026 06:01:53 +0000 (UTC)","by blackfin.pond.sub.org (Postfix, from userid 1000)\n id 291A021E6937; Sat, 28 Mar 2026 07:01:51 +0100 (CET)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1774677722;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n in-reply-to:in-reply-to:references:references;\n bh=LOl67eVYjM6XwA+2aoAT/RR6VujgC2WWk7a6aW7H6AI=;\n b=ZuDggVp99Z7LgOLNPmqXCggHXhuT+gJmUx7Z8UuQ13Yqv6Qo5vyECXdOTIJJ9OaaU+9tvr\n drzVUu0MDcFTcg+CNdbJIx4HGp2Hu6IqyHliUsf9C3LIepB9ygojUX3Dvu+RGjERrsRQVa\n OeQ6t8QerFAd2oBktPRfDX5/Jr5WdWg=","X-MC-Unique":"QK3TLCZJNl6B8duKTuTrnw-1","X-Mimecast-MFC-AGG-ID":"QK3TLCZJNl6B8duKTuTrnw_1774677715","From":"Markus Armbruster <armbru@redhat.com>","To":"Alireza Sanaee <alireza.sanaee@huawei.com>","Cc":"<qemu-devel@nongnu.org>,  <anisa.su@samsung.com>,\n <berrange@redhat.com>,  <eblake@redhat.com>,\n <jonathan.cameron@huawei.com>,  <linux-cxl@vger.kernel.org>,\n <linuxarm@huawei.com>,  <lizhijian@fujitsu.com>,  <mst@redhat.com>,\n <pbonzini@redhat.com>,  <gourry@gourry.net>,  <nifan.cxl@gmail.com>,\n <me@linux.beauty>","Subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","In-Reply-To":"<20260327151811.00005564.alireza.sanaee@huawei.com> (Alireza\n Sanaee's message of \"Fri, 27 Mar 2026 15:18:11 +0000\")","References":"<20260325184259.366-1-alireza.sanaee@huawei.com>\n <20260325184259.366-10-alireza.sanaee@huawei.com>\n <87mrzuei5f.fsf@pond.sub.org>\n <20260327151811.00005564.alireza.sanaee@huawei.com>","Date":"Sat, 28 Mar 2026 07:01:51 +0100","Message-ID":"<87zf3s1ohc.fsf@pond.sub.org>","User-Agent":"Gnus/5.13 (Gnus v5.13)","MIME-Version":"1.0","Content-Type":"text/plain","X-Scanned-By":"MIMEDefang 3.0 on 10.30.177.17","Received-SPF":"pass client-ip=170.10.129.124; envelope-from=armbru@redhat.com;\n helo=us-smtp-delivery-124.mimecast.com","X-Spam_score_int":"-20","X-Spam_score":"-2.1","X-Spam_bar":"--","X-Spam_report":"(-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001,\n DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,\n RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001,\n RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001,\n SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development <qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<https://lists.nongnu.org/archive/html/qemu-devel>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}},{"id":3671726,"web_url":"http://patchwork.ozlabs.org/comment/3671726/","msgid":"<20260331155044.0000603d.alireza.sanaee@huawei.com>","list_archive_url":null,"date":"2026-03-31T14:50:44","subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","submitter":{"id":90159,"url":"http://patchwork.ozlabs.org/api/people/90159/","name":"Alireza Sanaee","email":"alireza.sanaee@huawei.com"},"content":"On Sat, 28 Mar 2026 07:01:51 +0100\nMarkus Armbruster <armbru@redhat.com> wrote:\n\n+CC Ira\n\nHi Markus,\n\nPlease look inline. I believe Ira might be able to help and we can see what he thinks.\n\n> Alireza Sanaee <alireza.sanaee@huawei.com> writes:\n> \n> > On Thu, 26 Mar 2026 16:15:40 +0100\n> > Markus Armbruster <armbru@redhat.com> wrote:\n> >\n> > Hi Markus,\n> >\n> > This commit adds a test command to check whether an extent (a piece of memory region) has been released or not by the guest.\n> > The process of removal is highly asynchronous, that's why I needed to add a new command to check it.\n> >\n> > I would be happy to drop this patch, as this is extra.  \n> \n> So your motivation for adding the command is \"just\" testing.  Correct?\n\nI wrote tests to make sure extents were released, and I used this QMP command to check.\n\nNow there is background about extents where DCD was developed in Linux by @Ira, CCed [1].\n\nIn the DCD extent tracking section of the CXL spec, I see some commands \nrelated to getting the extent list, maybe Ira can comment here. To be fair, knowing if an extent\nwas released or not is a useful information in general from orchestrator perspective.\n\n[1] https://patchew.org/linux/20250413-dcd-type2-upstream-v9-0-1d4911a0b365@intel.com/\n\n> \n> Can you think of other uses?\n> \n> In particular, would a management application need this query to monitor\n> removal?\n\nI think management will get a signal on the removal given the schema in Ira's Linux kernel \npatchset. I do not think this is implemented in QEMU at least (I might be missing something).\n\n> \n> The description of feature @unstable may need to be adjusted for the\n> answers we work out here.\n\nAbsolutely.\n\n> \n> >\n> > Thanks,\n> > Ali  \n> \n>","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":"legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)","Received":["from lists.gnu.org (lists.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4flWKn2RbNz1y1q\n\tfor <incoming@patchwork.ozlabs.org>; Wed, 01 Apr 2026 01:51:57 +1100 (AEDT)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from <qemu-devel-bounces@nongnu.org>)\n\tid 1w7aR5-0005WN-Ee; Tue, 31 Mar 2026 10:51:19 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <alireza.sanaee@huawei.com>)\n id 1w7aQx-0005VN-9U\n for qemu-devel@nongnu.org; Tue, 31 Mar 2026 10:51:13 -0400","from frasgout.his.huawei.com ([185.176.79.56])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <alireza.sanaee@huawei.com>)\n id 1w7aQu-0000uC-3z\n for qemu-devel@nongnu.org; Tue, 31 Mar 2026 10:51:11 -0400","from mail.maildlp.com (unknown [172.18.224.83])\n by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4flWJ76QhRzJ4681;\n Tue, 31 Mar 2026 22:50:31 +0800 (CST)","from dubpeml500005.china.huawei.com (unknown [7.214.145.207])\n by mail.maildlp.com (Postfix) with ESMTPS id 7C61440575;\n Tue, 31 Mar 2026 22:50:50 +0800 (CST)","from localhost (10.203.177.99) by dubpeml500005.china.huawei.com\n (7.214.145.207) with Microsoft SMTP Server (version=TLS1_2,\n cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 31 Mar\n 2026 15:50:49 +0100"],"Date":"Tue, 31 Mar 2026 15:50:44 +0100","To":"Markus Armbruster <armbru@redhat.com>","CC":"<qemu-devel@nongnu.org>, <anisa.su@samsung.com>, <berrange@redhat.com>,\n <eblake@redhat.com>, <jonathan.cameron@huawei.com>,\n <linux-cxl@vger.kernel.org>, <linuxarm@huawei.com>, <lizhijian@fujitsu.com>,\n <mst@redhat.com>, <pbonzini@redhat.com>, <gourry@gourry.net>,\n <nifan.cxl@gmail.com>, <me@linux.beauty>, <ira.weiny@intel.com>","Subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","Message-ID":"<20260331155044.0000603d.alireza.sanaee@huawei.com>","In-Reply-To":"<87zf3s1ohc.fsf@pond.sub.org>","References":"<20260325184259.366-1-alireza.sanaee@huawei.com>\n <20260325184259.366-10-alireza.sanaee@huawei.com>\n <87mrzuei5f.fsf@pond.sub.org>\n <20260327151811.00005564.alireza.sanaee@huawei.com>\n <87zf3s1ohc.fsf@pond.sub.org>","Organization":"Huawei","X-Mailer":"Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32)","MIME-Version":"1.0","Content-Type":"text/plain; charset=\"US-ASCII\"","Content-Transfer-Encoding":"7bit","X-Originating-IP":"[10.203.177.99]","X-ClientProxiedBy":"lhrpeml500012.china.huawei.com (7.191.174.4) To\n dubpeml500005.china.huawei.com (7.214.145.207)","Received-SPF":"pass client-ip=185.176.79.56;\n envelope-from=alireza.sanaee@huawei.com; helo=frasgout.his.huawei.com","X-Spam_score_int":"-21","X-Spam_score":"-2.2","X-Spam_bar":"--","X-Spam_report":"(-2.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3,\n RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01,\n RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=1, RCVD_IN_VALIDITY_RPBL_BLOCKED=1,\n SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development <qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<https://lists.nongnu.org/archive/html/qemu-devel>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Reply-to":"Alireza Sanaee <alireza.sanaee@huawei.com>","From":"Alireza Sanaee via qemu development <qemu-devel@nongnu.org>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}},{"id":3672205,"web_url":"http://patchwork.ozlabs.org/comment/3672205/","msgid":"<87tstu29kx.fsf@pond.sub.org>","list_archive_url":null,"date":"2026-04-01T11:39:42","subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","submitter":{"id":2645,"url":"http://patchwork.ozlabs.org/api/people/2645/","name":"Markus Armbruster","email":"armbru@redhat.com"},"content":"Alireza Sanaee <alireza.sanaee@huawei.com> writes:\n\n> On Sat, 28 Mar 2026 07:01:51 +0100\n> Markus Armbruster <armbru@redhat.com> wrote:\n>\n> +CC Ira\n>\n> Hi Markus,\n>\n> Please look inline. I believe Ira might be able to help and we can see what he thinks.\n>\n>> Alireza Sanaee <alireza.sanaee@huawei.com> writes:\n>> \n>> > On Thu, 26 Mar 2026 16:15:40 +0100\n>> > Markus Armbruster <armbru@redhat.com> wrote:\n>> >\n>> > Hi Markus,\n>> >\n>> > This commit adds a test command to check whether an extent (a piece of memory region) has been released or not by the guest.\n>> > The process of removal is highly asynchronous, that's why I needed to add a new command to check it.\n>> >\n>> > I would be happy to drop this patch, as this is extra.  \n>> \n>> So your motivation for adding the command is \"just\" testing.  Correct?\n>\n> I wrote tests to make sure extents were released, and I used this QMP command to check.\n\nAs long as this is the only known use case, we want\n\n    # @unstable: This command is meant for debugging.\n\nin the QAPI schema.\n\n> Now there is background about extents where DCD was developed in Linux by @Ira, CCed [1].\n>\n> In the DCD extent tracking section of the CXL spec, I see some commands \n> related to getting the extent list, maybe Ira can comment here. To be fair, knowing if an extent\n> was released or not is a useful information in general from orchestrator perspective.\n>\n> [1] https://patchew.org/linux/20250413-dcd-type2-upstream-v9-0-1d4911a0b365@intel.com/\n\nIf we believe there are other uses, but we're unsure the command\nactually serves them:\n\n    # @unstable: This command is experimental.\n\n>> Can you think of other uses?\n>> \n>> In particular, would a management application need this query to monitor\n>> removal?\n>\n> I think management will get a signal on the removal given the schema in Ira's Linux kernel \n> patchset. I do not think this is implemented in QEMU at least (I might be missing something).\n\nI'm getting a feeling of \"this is underbaked\" :)  But that's for the CXL\nmaintainers to judge.\n\n>> The description of feature @unstable may need to be adjusted for the\n>> answers we work out here.\n>\n> Absolutely.\n>\n>> \n>> >\n>> > Thanks,\n>> > Ali  \n>> \n>>","headers":{"Return-Path":"<qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org>","X-Original-To":"incoming@patchwork.ozlabs.org","Delivered-To":"patchwork-incoming@legolas.ozlabs.org","Authentication-Results":["legolas.ozlabs.org;\n\tdkim=pass (1024-bit key;\n unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256\n header.s=mimecast20190719 header.b=RWAhoLKZ;\n\tdkim-atps=neutral","legolas.ozlabs.org;\n spf=pass (sender SPF authorized) smtp.mailfrom=nongnu.org\n (client-ip=209.51.188.17; helo=lists.gnu.org;\n envelope-from=qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org;\n receiver=patchwork.ozlabs.org)"],"Received":["from lists.gnu.org (lists.gnu.org [209.51.188.17])\n\t(using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits))\n\t(No client certificate requested)\n\tby legolas.ozlabs.org (Postfix) with ESMTPS id 4fm32p5k3nz1yFv\n\tfor <incoming@patchwork.ozlabs.org>; Wed, 01 Apr 2026 22:40:50 +1100 (AEDT)","from localhost ([::1] helo=lists1p.gnu.org)\n\tby lists.gnu.org with esmtp (Exim 4.90_1)\n\t(envelope-from <qemu-devel-bounces@nongnu.org>)\n\tid 1w7tvV-0004lE-Q2; Wed, 01 Apr 2026 07:40:01 -0400","from eggs.gnu.org ([2001:470:142:3::10])\n by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w7tvS-0004ku-7z\n for qemu-devel@nongnu.org; Wed, 01 Apr 2026 07:39:58 -0400","from us-smtp-delivery-124.mimecast.com ([170.10.133.124])\n by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)\n (Exim 4.90_1) (envelope-from <armbru@redhat.com>) id 1w7tvO-0007Ff-Uj\n for qemu-devel@nongnu.org; Wed, 01 Apr 2026 07:39:57 -0400","from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com\n (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by\n relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-202-qe4Ff5YzMWiw4qyQPLAQqg-1; Wed,\n 01 Apr 2026 07:39:47 -0400","from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com\n (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS\n id 0B930195607D; Wed,  1 Apr 2026 11:39:46 +0000 (UTC)","from blackfin.pond.sub.org (unknown [10.44.22.6])\n by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with\n ESMTPS\n id 17205180058B; Wed,  1 Apr 2026 11:39:45 +0000 (UTC)","by blackfin.pond.sub.org (Postfix, from userid 1000)\n id BAB5321E6A28; Wed, 01 Apr 2026 13:39:42 +0200 (CEST)"],"DKIM-Signature":"v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1775043593;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n in-reply-to:in-reply-to:references:references;\n bh=mqezalPl4i3JBcgLVBe3bFLBNdF5OgFM/6xHTa3bquo=;\n b=RWAhoLKZGbhzsSnZKAULu2ihCHm1wy9eKnhWQVbv8dMpYTnHQ55I70D2Tny/xa8Ud1iScC\n 2vOWJLztKQzsuEywZQXLa9MtDbRbAgeZ9f2A/OToYZ3ald4GfE0kFTWc1AVubpw9WnJXtT\n H9zbJgr/ung9Y9cS/5nBhN0KD6kNvS0=","X-MC-Unique":"qe4Ff5YzMWiw4qyQPLAQqg-1","X-Mimecast-MFC-AGG-ID":"qe4Ff5YzMWiw4qyQPLAQqg_1775043586","From":"Markus Armbruster <armbru@redhat.com>","To":"Alireza Sanaee <alireza.sanaee@huawei.com>","Cc":"<qemu-devel@nongnu.org>,  <anisa.su@samsung.com>,\n <berrange@redhat.com>,  <eblake@redhat.com>,\n <jonathan.cameron@huawei.com>,  <linux-cxl@vger.kernel.org>,\n <linuxarm@huawei.com>,  <lizhijian@fujitsu.com>,  <mst@redhat.com>,\n <pbonzini@redhat.com>,  <gourry@gourry.net>,  <nifan.cxl@gmail.com>,\n <me@linux.beauty>,  <ira.weiny@intel.com>","Subject":"Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity\n extent release","In-Reply-To":"<20260331155044.0000603d.alireza.sanaee@huawei.com> (Alireza\n Sanaee's message of \"Tue, 31 Mar 2026 15:50:44 +0100\")","References":"<20260325184259.366-1-alireza.sanaee@huawei.com>\n <20260325184259.366-10-alireza.sanaee@huawei.com>\n <87mrzuei5f.fsf@pond.sub.org>\n <20260327151811.00005564.alireza.sanaee@huawei.com>\n <87zf3s1ohc.fsf@pond.sub.org>\n <20260331155044.0000603d.alireza.sanaee@huawei.com>","Date":"Wed, 01 Apr 2026 13:39:42 +0200","Message-ID":"<87tstu29kx.fsf@pond.sub.org>","User-Agent":"Gnus/5.13 (Gnus v5.13)","MIME-Version":"1.0","Content-Type":"text/plain","X-Scanned-By":"MIMEDefang 3.4.1 on 10.30.177.111","Received-SPF":"pass client-ip=170.10.133.124; envelope-from=armbru@redhat.com;\n helo=us-smtp-delivery-124.mimecast.com","X-Spam_score_int":"27","X-Spam_score":"2.7","X-Spam_bar":"++","X-Spam_report":"(2.7 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.54,\n DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,\n RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.01, RCVD_IN_SBL_CSS=3.335,\n RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=1, RCVD_IN_VALIDITY_RPBL_BLOCKED=1,\n SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no","X-Spam_action":"no action","X-BeenThere":"qemu-devel@nongnu.org","X-Mailman-Version":"2.1.29","Precedence":"list","List-Id":"qemu development <qemu-devel.nongnu.org>","List-Unsubscribe":"<https://lists.nongnu.org/mailman/options/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>","List-Archive":"<https://lists.nongnu.org/archive/html/qemu-devel>","List-Post":"<mailto:qemu-devel@nongnu.org>","List-Help":"<mailto:qemu-devel-request@nongnu.org?subject=help>","List-Subscribe":"<https://lists.nongnu.org/mailman/listinfo/qemu-devel>,\n <mailto:qemu-devel-request@nongnu.org?subject=subscribe>","Errors-To":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org","Sender":"qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org"}}]