From: Markus Armbruster <armbru@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: jonathan.cameron@huawei.com, ira.weiny@intel.com,
alucerop@amd.com, a.manzanares@samsung.com,
dongjoo.seo1@samsung.com, mst@redhat.com,
marcel.apfelbaum@gmail.com, linux-cxl@vger.kernel.org,
qemu-devel@nongnu.org
Subject: Re: [PATCH 3/5] hw/cxl: Allow BI by default in Window restrictions
Date: Thu, 18 Dec 2025 10:18:17 +0100 [thread overview]
Message-ID: <87wm2ki1wm.fsf@pond.sub.org> (raw)
In-Reply-To: <20251103195209.1319917-4-dave@stgolabs.net> (Davidlohr Bueso's message of "Mon, 3 Nov 2025 11:52:07 -0800")
Davidlohr Bueso <dave@stgolabs.net> writes:
> Update the CFMW restrictions to also permit Back-Invalidate
> flows by default, which is aligned with the no-restrictions
> policy.
>
> While at it, document the 'restrictions=' option.
I'd split the patch. Up to you.
> Tested-by: Dongjoo Seo <dongjoo.seo1@samsung.com>
> Signed-off-by: Davidlohr Bueso <dave@stgolabs.net>
> ---
> hw/cxl/cxl-host.c | 2 +-
> qapi/machine.json | 3 ++-
> qemu-options.hx | 4 +++-
> 3 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/hw/cxl/cxl-host.c b/hw/cxl/cxl-host.c
> index e420b25176a6..ed0c76a31980 100644
> --- a/hw/cxl/cxl-host.c
> +++ b/hw/cxl/cxl-host.c
> @@ -64,7 +64,7 @@ static void cxl_fixed_memory_window_config(CXLFixedMemoryWindowOptions *object,
> if (object->has_restrictions) {
> fw->restrictions = object->restrictions;
> } else {
> - fw->restrictions = 0xf; /* No restrictions */
> + fw->restrictions = 0x2f; /* No restrictions */
> }
>
> fw->targets = g_malloc0_n(fw->num_targets, sizeof(*fw->targets));
> diff --git a/qapi/machine.json b/qapi/machine.json
> index 225690d2986a..85e31432b038 100644
> --- a/qapi/machine.json
> +++ b/qapi/machine.json
> @@ -555,7 +555,8 @@
> # BIT(2) - Volatile
> # BIT(3) - Persistent
> # BIT(4) - Fixed Device Config
> -# Default is 0xF
> +# BIT(5) - BI
> +# Default is 0x2F
> #
> # @targets: Target root bridge IDs from -device ...,id=<ID> for each
> # root bridge.
This changes the default of @restrictions. No problem since
@restrictions has not been in any release. If it was, we'd have to
consider backward compatibility.
[...]
next prev parent reply other threads:[~2025-12-18 9:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 19:52 [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 1/5] hw/pcie: Support enabling flit mode Davidlohr Bueso
2025-12-18 16:31 ` Jonathan Cameron
2025-12-18 16:31 ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 2/5] hw/cxl: Refactor component register initialization Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 3/5] hw/cxl: Allow BI by default in Window restrictions Davidlohr Bueso
2025-12-18 9:18 ` Markus Armbruster [this message]
2025-12-18 15:48 ` Jonathan Cameron
2025-12-18 15:48 ` Jonathan Cameron via
2025-12-18 15:59 ` Markus Armbruster
2025-12-19 17:53 ` Jonathan Cameron
2025-12-19 17:53 ` Jonathan Cameron via
2025-11-03 19:52 ` [PATCH 4/5] hw/cxl: Support type3 HDM-DB Davidlohr Bueso
2025-11-03 19:52 ` [PATCH 5/5] hw/cxl: Remove register special_ops->read() Davidlohr Bueso
2025-12-16 1:12 ` [PATCH v4 -qemu 0/5] hw/cxl: Support Back-Invalidate Davidlohr Bueso
2025-12-17 13:59 ` Jonathan Cameron
2025-12-17 13:59 ` Jonathan Cameron via
2025-12-23 11:53 ` Jonathan Cameron
2025-12-23 11:53 ` Jonathan Cameron via
2025-12-30 18:23 ` Davidlohr Bueso
2026-01-02 16:35 ` Jonathan Cameron
2026-01-02 16:35 ` Jonathan Cameron via
2025-12-16 6:53 ` Markus Armbruster
2025-12-16 15:24 ` Davidlohr Bueso
2025-12-17 7:51 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2025-09-30 3:21 [PATCH v3 " Davidlohr Bueso
2025-09-30 3:21 ` [PATCH 3/5] hw/cxl: Allow BI by default in Window restrictions Davidlohr Bueso
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=87wm2ki1wm.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=a.manzanares@samsung.com \
--cc=alucerop@amd.com \
--cc=dave@stgolabs.net \
--cc=dongjoo.seo1@samsung.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@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.