From: Markus Armbruster <armbru@redhat.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <qemu-devel@nongnu.org>, <anisa.su@samsung.com>,
<berrange@redhat.com>, <eblake@redhat.com>,
<jonathan.cameron@huawei.com>, <linux-cxl@vger.kernel.org>,
<linuxarm@huawei.com>, <lizhijian@fujitsu.com>,
<mst@redhat.com>, <pbonzini@redhat.com>, <gourry@gourry.net>,
<nifan.cxl@gmail.com>, <me@linux.beauty>
Subject: Re: [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity extent release
Date: Sat, 28 Mar 2026 07:01:51 +0100 [thread overview]
Message-ID: <87zf3s1ohc.fsf@pond.sub.org> (raw)
In-Reply-To: <20260327151811.00005564.alireza.sanaee@huawei.com> (Alireza Sanaee's message of "Fri, 27 Mar 2026 15:18:11 +0000")
Alireza Sanaee <alireza.sanaee@huawei.com> writes:
> On Thu, 26 Mar 2026 16:15:40 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
> Hi Markus,
>
> This commit adds a test command to check whether an extent (a piece of memory region) has been released or not by the guest.
> The process of removal is highly asynchronous, that's why I needed to add a new command to check it.
>
> I would be happy to drop this patch, as this is extra.
So your motivation for adding the command is "just" testing. Correct?
Can you think of other uses?
In particular, would a management application need this query to monitor
removal?
The description of feature @unstable may need to be adjusted for the
answers we work out here.
>
> Thanks,
> Ali
next prev parent reply other threads:[~2026-03-28 6:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 18:42 [QEMU PATCH 0/9] Application Specific Tagged Memory Support in CXL Type 3 Devices Alireza Sanaee
2026-03-25 18:42 ` [PATCH 1/9] hw/mem: Add tag support to generic host memory backends Alireza Sanaee
2026-03-26 10:42 ` Markus Armbruster
2026-03-26 11:29 ` Alireza Sanaee
2026-03-26 13:01 ` Markus Armbruster
2026-03-26 13:04 ` Alireza Sanaee
2026-03-25 18:42 ` [PATCH 2/9] hw/cxl: Allow initializing type3 device with no backing device Alireza Sanaee
2026-03-25 18:42 ` [PATCH 3/9] hw/cxl: Hook up tagged host memory backends at runtime for DC extents Alireza Sanaee
2026-03-25 18:42 ` [PATCH 4/9] hw/cxl: Carry backend metadata in DC extent records Alireza Sanaee
2026-03-25 18:42 ` [PATCH 5/9] hw/cxl: Map lazy memory backend after host acceptance Alireza Sanaee
2026-03-30 8:24 ` Anisa Su
2026-03-30 17:18 ` Anisa Su
2026-03-25 18:42 ` [PATCH 6/9] hw/cxl: Create direct fixed-window aliases for accepted extents Alireza Sanaee
2026-03-25 18:42 ` [PATCH 7/9] hw/cxl: Add release-time teardown for direct-mapped extents Alireza Sanaee
2026-03-25 18:42 ` [PATCH 8/9] hw/cxl: Add tag-based dynamic-capacity release support Alireza Sanaee
2026-03-30 18:03 ` Anisa Su
2026-03-31 14:53 ` Alireza Sanaee
2026-03-25 18:42 ` [PATCH 9/9] hw/cxl: Add QMP status query for dynamic-capacity extent release Alireza Sanaee
2026-03-26 15:15 ` Markus Armbruster
2026-03-27 15:18 ` Alireza Sanaee
2026-03-28 6:01 ` Markus Armbruster [this message]
2026-03-31 14:50 ` Alireza Sanaee
2026-04-01 11:39 ` Markus Armbruster
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=87zf3s1ohc.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alireza.sanaee@huawei.com \
--cc=anisa.su@samsung.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=gourry@gourry.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lizhijian@fujitsu.com \
--cc=me@linux.beauty \
--cc=mst@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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