Linux CXL
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <dave.jiang@intel.com>,
	Adam Manzanares <a.manzanares@samsung.com>
Subject: Re: [PATCH] Documentation: CXL Maturity Map
Date: Thu, 20 Jun 2024 18:45:43 +0100	[thread overview]
Message-ID: <20240620184543.00004ff1@Huawei.com> (raw)
In-Reply-To: <6670bdb69f996_3101294b8@dwillia2-xfh.jf.intel.com.notmuch>

ling, or kernel enabling not required
> > > +
> > > +Feature and Capabilities
> > > +========================
> > > +
> > > +Enumeration / Provisioning
> > > +--------------------------
> > > +All of the fundamental enumeration an object model of the subsystem is
> > > +in place, but there are several corner cases that are pending closure.
> > > +  
> > 
> > Feels like we should in passing mention that we support none of the
> > bits of CXL fabrics that are host visible (so mainly G-FAM I think).
> > 
> > [0] Fabrics / G-FAM (chapter 7)
> > [0] Global Access Enpoint  
> 
> Are those [0] or [X], not even sure what the kernel is expected to do with those?

I'm not 100% sure, but they are host programmable and there
are a bunch of more general structures to program that are
'kind of like' the hdm decoders with stuff like interleave
setup.  So I think [0] but I've really not figure out the expected
software model for that stuff yet.

Jonathan


  reply	other threads:[~2024-06-20 17:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240617165830uscas1p12e867fc6ad52fa7cfa32955f3150dd6f@uscas1p1.samsung.com>
2024-05-25  0:53 ` [PATCH] Documentation: CXL Maturity Map Dan Williams
2024-06-06  3:23   ` Alison Schofield
2024-06-17 22:25     ` Davidlohr Bueso
2024-06-17 22:38     ` Dan Williams
2024-06-06 14:40   ` Jonathan Cameron
2024-06-17 22:50     ` Dan Williams
2024-06-20 17:45       ` Jonathan Cameron [this message]
2024-06-17 16:58   ` Adam Manzanares
2024-06-17 22:54     ` Dan Williams
2024-06-27 17:52       ` Adam Manzanares
2024-06-19 16:02   ` Alejandro Lucero Palau
2024-07-03 23:26     ` Dan Williams

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=20240620184543.00004ff1@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.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