From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linuxarm@huawei.com>,
<eblake@redhat.com>, <armbru@redhat.com>, <berrange@redhat.com>,
<pbonzini@redhat.com>, <mst@redhat.com>, <lizhijian@fujitsu.com>,
<anisa.su@samsung.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [RFC PATCH 6/7] hw/cxl: Add remove alias functionality for extent direct mapping
Date: Fri, 6 Feb 2026 12:43:42 +0000 [thread overview]
Message-ID: <20260206124342.00001f75@huawei.com> (raw)
In-Reply-To: <20251127225526.700-7-alireza.sanaee@huawei.com>
On Thu, 27 Nov 2025 22:55:24 +0000
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> Remove alias related to an extent when the extent is longer available,
> from removed from the VM.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
I'd combine with previous. Otherwise we are broken in between.
I guess you could add a temporary error return to the remove path in previous
patch if they really don't more sense combined.
Jonathan
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linuxarm@huawei.com>,
<eblake@redhat.com>, <armbru@redhat.com>, <berrange@redhat.com>,
<pbonzini@redhat.com>, <mst@redhat.com>, <lizhijian@fujitsu.com>,
<anisa.su@samsung.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [RFC PATCH 6/7] hw/cxl: Add remove alias functionality for extent direct mapping
Date: Fri, 6 Feb 2026 12:43:42 +0000 [thread overview]
Message-ID: <20260206124342.00001f75@huawei.com> (raw)
In-Reply-To: <20251127225526.700-7-alireza.sanaee@huawei.com>
On Thu, 27 Nov 2025 22:55:24 +0000
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> Remove alias related to an extent when the extent is longer available,
> from removed from the VM.
>
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
I'd combine with previous. Otherwise we are broken in between.
I guess you could add a temporary error return to the remove path in previous
patch if they really don't more sense combined.
Jonathan
next prev parent reply other threads:[~2026-02-06 12:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 22:55 [RFC QEMU PATCH 0/7] Application Specific Tagged Memory Support in CXL Type 3 Devices Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2025-11-27 22:55 ` [RFC PATCH 1/7] hw/mem: Add tagged memory backend object Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:16 ` Jonathan Cameron
2026-02-06 12:16 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 2/7] hw/cxl: Allow initializing type3 device with no backing device Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:28 ` Jonathan Cameron
2026-02-06 12:28 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 3/7] hw/cxl: Change Extent add/remove APIs for lazy memory backend Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:30 ` Jonathan Cameron
2026-02-06 12:30 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 4/7] hw/cxl: Map lazy memory backend after host acceptance Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:33 ` Jonathan Cameron
2026-02-06 12:33 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 5/7] hw/cxl: Add performant direct mapping for extents Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:41 ` Jonathan Cameron
2026-02-06 12:41 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 6/7] hw/cxl: Add remove alias functionality for extent direct mapping Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:43 ` Jonathan Cameron [this message]
2026-02-06 12:43 ` Jonathan Cameron via qemu development
2025-11-27 22:55 ` [RFC PATCH 7/7] hw/cxl: Add tag-based removal functionality Alireza Sanaee
2025-11-27 22:55 ` Alireza Sanaee via
2026-02-06 12:49 ` Jonathan Cameron
2026-02-06 12:49 ` Jonathan Cameron via qemu development
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=20260206124342.00001f75@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alireza.sanaee@huawei.com \
--cc=anisa.su@samsung.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lizhijian@fujitsu.com \
--cc=mst@redhat.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 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.