From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: Alireza Sanaee <alireza.sanaee@huawei.com>
Cc: <qemu-devel@nongnu.org>, <gourry@gourry.net>,
<lizhijian@fujitsu.com>, <anisa.su887@gmail.com>,
<armbru@redhat.com>, <david@kernel.org>, <imammedo@redhat.com>,
<linuxarm@huawei.com>, <mst@redhat.com>, <nifan.cxl@gmail.com>,
<peterx@redhat.com>, <philmd@linaro.org>, <pbonzini@redhat.com>,
<venkataravis@micron.com>, <xiaoguangrong.eric@gmail.com>
Subject: Re: [PATCH v7 3/3] hw/cxl: Add a performant (and correct) path for the non interleaved cases
Date: Fri, 6 Mar 2026 15:15:15 +0000 [thread overview]
Message-ID: <20260306151515.000047a1@huawei.com> (raw)
In-Reply-To: <20260306121151.883-4-alireza.sanaee@huawei.com>
On Fri, 6 Mar 2026 12:11:51 +0000
Alireza Sanaee <alireza.sanaee@huawei.com> wrote:
> The CXL address to device decoding logic is complex because of the need to
> correctly decode fine grained interleave. The current implementation
> prevents use with KVM where executed instructions may reside in that memory
> and gives very slow performance even in TCG.
>
> In many real cases non interleaved memory configurations are useful and for
> those we can use a more conventional memory region alias allowing similar
> performance to other memory in the system.
>
> Whether this fast path is applicable can be established once the full set
> of HDM decoders has been committed (in whatever order the guest decides to
> commit them). As such a check is performed on each commit/uncommit of HDM
> decoder to establish if the alias should be added or removed.
>
> Reviewed-by: Li Zhijian <lizhijian@fujitsu.com>
> Co-developed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> Signed-off-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Changes look good to me. Thanks for the quick turn around.
Jonathan
> Signed-off-by: Alireza Sanaee <alireza.sanaee@huawei.com>
next prev parent reply other threads:[~2026-03-06 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 12:11 [PATCH v7 0/3] hw/cxl: Add a performant (and correct) path for the non interleaved cases Alireza Sanaee via qemu development
2026-03-06 12:11 ` [PATCH v7 1/3] hw/cxl: Use HPA in cxl_cfmws_find_device() rather than offset in window Alireza Sanaee via qemu development
2026-03-06 16:15 ` Gregory Price
2026-03-06 12:11 ` [PATCH v7 2/3] hw/cxl: Allow cxl_cfmws_find_device() to filter on whether interleaved paths are accepted Alireza Sanaee via qemu development
2026-03-06 15:12 ` Jonathan Cameron via qemu development
2026-03-06 16:15 ` Gregory Price
2026-03-06 12:11 ` [PATCH v7 3/3] hw/cxl: Add a performant (and correct) path for the non interleaved cases Alireza Sanaee via qemu development
2026-03-06 15:15 ` Jonathan Cameron via qemu development [this message]
2026-03-06 16:16 ` Gregory Price
2026-03-06 13:29 ` [PATCH v7 0/3] " Alireza Sanaee via qemu development
2026-03-06 15:19 ` Jonathan Cameron via qemu development
2026-03-06 16:16 ` Gregory Price
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=20260306151515.000047a1@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=alireza.sanaee@huawei.com \
--cc=anisa.su887@gmail.com \
--cc=armbru@redhat.com \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=imammedo@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=lizhijian@fujitsu.com \
--cc=mst@redhat.com \
--cc=nifan.cxl@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=venkataravis@micron.com \
--cc=xiaoguangrong.eric@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.