From: Ira Weiny <ira.weiny@intel.com>
To: <nifan@outlook.com>, <qemu-devel@nongnu.org>
Cc: <jonathan.cameron@huawei.com>, <linux-cxl@vger.kernel.org>,
<gregory.price@memverge.com>, <hchkuo@avery-design.com.tw>,
<cbrowy@avery-design.com>, <ira.weiny@intel.com>,
<dan.j.williams@intel.com>, <a.manzanares@samsung.com>,
<dave@stgolabs.net>, <nmtadam.samsung@gmail.com>,
Fan Ni <nifan@outlook.com>
Subject: Re: [Qemu PATCH 0/9] Enabling DCD emulation support in Qemu
Date: Sat, 22 Jul 2023 21:57:00 -0700 [thread overview]
Message-ID: <64bcb31c9a8dc_760de2941@iweiny-mobl.notmuch> (raw)
In-Reply-To: <SG2PR06MB33976BB3F9C47CBE08F02D09B23EA@SG2PR06MB3397.apcprd06.prod.outlook.com>
nifan@ wrote:
> From: Fan Ni <nifan@outlook.com>
>
> The patch series provides dynamic capacity device (DCD) emulation in Qemu.
> More specifically, it provides the following functionalities:
> 1. Extended type3 memory device to support DC regions and extents.
> 2. Implemented DCD related mailbox command support in CXL r3.0: 8.2.9.8.9.
> 3. ADD QMP interfaces for adding and releasing DC extents to simulate FM
> functions for DCD described in cxl r3.0: 7.6.7.6.5 and 7.6.7.6.6.
> 4. Add new ct3d properties for DCD devices (host backend, number of dc
> regions, etc.)
> 5. Add read/write support from/to DC regions of the device.
> 6. Add mechanism to validate accessed to DC region address space.
>
Sorry I see them in this other thread now.
https://lore.kernel.org/all/SG2PR06MB3397F3E74A083607F7492FA4B23EA@SG2PR06MB3397.apcprd06.prod.outlook.com/
Thanks,
Ira
> A more detailed description can be found from the previously posted RFC[1].
>
> Compared to the previously posted RFC[1], following changes have been made:
> 1. Rebased the code on top of Jonathan's branch
> https://gitlab.com/jic23/qemu/-/tree/cxl-2023-05-25.
> 2. Extracted the rename of mem_size to a separated patch.(Jonathan)
> 3. Reordered the patch series to improve its readability.(Jonathan)
> 4. Split the validation of accesses to DC region address space as a separate
> patch.
> 5. Redesigned the QMP interfaces for adding and releasing DC extents to make
> them easier to understand and act like existing QMP interfaces (like the
> interface for cxl-inject-uncorrectable-errors). (Jonathan)
> 6. Updated dvsec range register setting to support DCD devices without static
> capacity.
> 7. Fixed other issues mentioned in the comments (Jonathan&Nathan Fontenot).
> 8. Fixed the format issues and checked with checkpatch.pl under qemu code dir.
>
>
> The code is tested with the DCD patch series at the kernel side[2]. The test
> is similar to those mentioned in the cover letter of [1].
>
>
> [1]: https://lore.kernel.org/all/20230511175609.2091136-1-fan.ni@samsung.com/
> [2]: https://lore.kernel.org/linux-cxl/649da378c28a3_968bb29420@iweiny-mobl.notmuch/T/#t
>
> Fan Ni (9):
> hw/cxl/cxl-mailbox-utils: Add dc_event_log_size field to output
> payload of identify memory device command
> hw/cxl/cxl-mailbox-utils: Add dynamic capacity region representative
> and mailbox command support
> include/hw/cxl/cxl_device: Rename mem_size as static_mem_size for
> type3 memory devices
> hw/mem/cxl_type3: Add support to create DC regions to type3 memory
> devices
> hw/mem/cxl_type3: Add host backend and address space handling for DC
> regions
> hw/mem/cxl_type3: Add DC extent list representative and get DC extent
> list mailbox support
> hw/cxl/cxl-mailbox-utils: Add mailbox commands to support add/release
> dynamic capacity response
> hw/cxl/events: Add qmp interfaces to add/release dynamic capacity
> extents
> hw/mem/cxl_type3: Add dpa range validation for accesses to dc regions
>
> hw/cxl/cxl-mailbox-utils.c | 421 +++++++++++++++++++++++++++-
> hw/mem/cxl_type3.c | 539 +++++++++++++++++++++++++++++++++---
> hw/mem/cxl_type3_stubs.c | 6 +
> include/hw/cxl/cxl_device.h | 49 +++-
> include/hw/cxl/cxl_events.h | 16 ++
> qapi/cxl.json | 49 ++++
> 6 files changed, 1034 insertions(+), 46 deletions(-)
>
> --
> 2.39.2
>
prev parent reply other threads:[~2023-07-23 4:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 20:36 [Qemu PATCH 0/9] Enabling DCD emulation support in Qemu nifan
2023-07-23 4:52 ` Ira Weiny
2023-07-24 8:57 ` Jonathan Cameron via
[not found] ` <CGME20230724164148uscas1p2094eb209cadef83526227eb62cdda65c@uscas1p2.samsung.com>
2023-07-24 16:41 ` Fan Ni
2023-07-23 4:57 ` Ira Weiny [this message]
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=64bcb31c9a8dc_760de2941@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=a.manzanares@samsung.com \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=gregory.price@memverge.com \
--cc=hchkuo@avery-design.com.tw \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan@outlook.com \
--cc=nmtadam.samsung@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).