All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Fan Ni <fan.ni@samsung.com>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
	"Singh, Naveen" <naveen.c.singh@intel.com>,
	<linux-cxl@vger.kernel.org>
Subject: Questions about the qemu DCD support in cxl-2023-09-13
Date: Thu, 21 Sep 2023 15:24:26 -0700	[thread overview]
Message-ID: <650cc29ab3f64_50d07294e7@iweiny-mobl.notmuch> (raw)

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.

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().

Ira

[1] https://gitlab.com/jic23/qemu/-/tree/cxl-2023-09-13

             reply	other threads:[~2023-09-21 22:24 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 ` Ira Weiny [this message]
2023-09-21 22:51   ` Questions about the qemu DCD support in cxl-2023-09-13 Fan Ni
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-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=650cc29ab3f64_50d07294e7@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=fan.ni@samsung.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 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.