From: fan <nifan.cxl@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Fan Ni <fan.ni@samsung.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
"Singh, Naveen" <naveen.c.singh@intel.com>,
linux-cxl@vger.kernel.org, a.manzanares@samsung.com,
dave@stgolabs.net, nmtadam.samsung@gmail.com
Subject: Re: Questions about the qemu DCD support in cxl-2023-09-13
Date: Mon, 23 Oct 2023 12:48:02 -0700 [thread overview]
Message-ID: <ZTbN8mAa256JWTFE@debian> (raw)
In-Reply-To: <650cc29ab3f64_50d07294e7@iweiny-mobl.notmuch>
On Thu, Sep 21, 2023 at 03:24:26PM -0700, Ira Weiny wrote:
> 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
Hi Ira,
FYI. I have updated the DCD emulation patch series based on feedbacks on
the previous version.
The new version is here:
https://github.com/moking/qemu-jic-clone/tree/dcd-dev
The code is based on Jonathan's branch cxl-2023-09-26.
The main changes include,
1. Update cxl_find_dc_region to detect the case the range of
the extent cross multiple DC regions.
2. Add comments to explain the checks performed in function
cxl_detect_malformed_extent_list. (Jonathan)
3. Minimize the checks in cmd_dcd_add_dyn_cap_rsp.(Jonathan)
4. Update total_extent_count in add/release dynamic capacity response function.
(Ira and Jorgen Hansen).
5. Fix the logic issue in test_bits and renamed it to
test_any_bits_set to clear its function.
6. Add pending extent list for add/release extent event.
7. When add/release extent response is received, use the pending list to
verify the extents are valid.
8. Add test_any_bits_set and cxl_insert_extent_to_extent_list declaration to
cxl_device.h so it can be used in different files.
9. Updated ct3d_qmp_cxl_event_log_enc to include dynamic capacity event log type.
10. Extract the functionality to delete extent from extent list to a helper
function.
11. Move the update of the bitmap which reflects which blocks are backed with
dc extents from the moment when a dc extent is offered to the moment when it
is accepted from the host.
I was able to test the DCD code you sent previously, let me know if you
find any issues.
Fan
next prev parent reply other threads:[~2023-10-23 19:48 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
2023-10-23 19:48 ` fan [this message]
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=ZTbN8mAa256JWTFE@debian \
--to=nifan.cxl@gmail.com \
--cc=a.manzanares@samsung.com \
--cc=dave@stgolabs.net \
--cc=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 \
--cc=nmtadam.samsung@gmail.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