Linux CXL
 help / color / mirror / Atom feed
From: Fan Ni <fan.ni@samsung.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
	"Singh, Naveen" <naveen.c.singh@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Subject: Re: Questions about the qemu DCD support in cxl-2023-09-13
Date: Thu, 21 Sep 2023 22:51:29 +0000	[thread overview]
Message-ID: <20230921225123.GA3690460@sjcvldevvm72> (raw)
In-Reply-To: <650cc29ab3f64_50d07294e7@iweiny-mobl.notmuch>

On Thu, Sep 21, 2023 at 03:24:26PM -0700, Ira Weiny wrote:

Hi Ira,

Thanks for reaching out.
For DCD, I think Jonathan's branch does not change much compared to the patch
series sent out except some obvious issues that blocks the test.

My initial plan was to update the patches after I have tested the
current version with more stable kernel DCD driver.

See below.


> Fan,
> 
> I'm working off of Jonathan's latest CXL branch with the DCD patches.[1]
> 
> I've been testing various things and so far I have a couple of questions.
> 
> 1) If the qmp command is used to add extents which overlap other extents
>    shouldn't that throw an error?  I don't see any validation of this and
>    I would think a real device would reject such a request from the FM.
> 

Yes. We do not have any validation for the overlapped extents here
in current code.

> 2) Where is CXLType3Dev->dc.total_extent_count set?  Attempting to add
>    extents prior to driver load does not seem to work.  And I think this
>    is because total_extent_count is 0 in cmd_dcd_get_dyn_cap_ext_list().

I am aware of the issue, yet have not got a chance to fix it. 

My understanding is whenever we complete adding/releasing
extents, we update it.

I will fix it and other issues mentioned in the comments in the next version.

Fan
> 
> Ira
> 
> [1] https://urldefense.com/v3/__https://gitlab.com/jic23/qemu/-/tree/cxl-2023-09-13__;!!EwVzqGoTKBqv-0DWAJBm!WrndoKsXHVaUoln-Jsq7MFRemLlcFYg788t_tDaFt1lS7WFhE2s_5hsI4-WuNzlgLOc0e0DgdcepR368SHU$ 

  reply	other threads:[~2023-09-21 22:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230921222437uscas1p158e5ceecab50dcb39e33811f567152d8@uscas1p1.samsung.com>
2023-09-21 22:24 ` Questions about the qemu DCD support in cxl-2023-09-13 Ira Weiny
2023-09-21 22:51   ` Fan Ni [this message]
2023-10-23 19:48   ` fan
2023-10-24 18:56     ` fan
2023-10-25  5:25       ` fan
2023-10-26  9:01         ` Jonathan Cameron
2023-10-26 16:58           ` Jonathan Cameron
2023-10-26 16:58             ` Jonathan Cameron
2023-10-27 16:34             ` fan
2023-10-31 17:18               ` Jonathan Cameron
2023-10-31 17:44                 ` fan

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=20230921225123.GA3690460@sjcvldevvm72 \
    --to=fan.ni@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=naveen.c.singh@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