mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Mayank Rana <mayank.rana@oss.qualcomm.com>
Cc: linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
	ira.weiny@intel.com, vishal.l.verma@intel.com,
	alison.schofield@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] cxl/hdm: Enforce CFMWS memory type policy at decoder commit time
Date: Mon, 13 Jul 2026 09:04:48 -0700	[thread overview]
Message-ID: <20260713160448.wvkpmbldmfciq4a3@offworld> (raw)
In-Reply-To: <20260711003341.2602368-1-mayank.rana@oss.qualcomm.com>

On Fri, 10 Jul 2026, Mayank Rana wrote:

>A CXL Fixed Memory Window Structure (CFMWS) in the ACPI CEDT table
>carries a restrictions field that describes the memory types a platform
>window supports.  cfmws_to_decoder_flags() translates this into
>CXL_DECODER_F_TYPE2 (HDM-DB permitted) and CXL_DECODER_F_TYPE3 (HDM-H
>permitted) flags on the root decoder.
>
>However, nothing currently prevents a caller from committing an endpoint
>or switch decoder whose target_type conflicts with the CFMWS policy:

Hi Mayank - please refer to the latest Back Invalidate patchset (v5)
for properly dealing with this:

https://lore.kernel.org/all/20260615145529.13848-1-dave@stgolabs.net/

Thanks,
Davidlohr

  parent reply	other threads:[~2026-07-13 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  0:33 Mayank Rana
2026-07-13 15:47 ` Dave Jiang
2026-07-15 22:26   ` Mayank Rana
2026-07-23 23:18     ` Mayank Rana
2026-07-23 23:47       ` Dave Jiang
2026-07-24 23:08         ` Mayank Rana
2026-07-25 18:29           ` Davidlohr Bueso
2026-07-13 16:04 ` Davidlohr Bueso [this message]
2026-07-15 22:35   ` Mayank Rana
  -- strict thread matches above, loose matches on Subject: below --
2026-07-09 21:47 Mayank Rana
2026-07-09 22:04 ` Mayank Rana

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=20260713160448.wvkpmbldmfciq4a3@offworld \
    --to=dave@stgolabs.net \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mayank.rana@oss.qualcomm.com \
    --cc=vishal.l.verma@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®