From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-cxl@vger.kernel.org, qemu-devel@nongnu.org,
svetly.todorov@memverge.com, nifan.cxl@gmail.com
Subject: Re: [PATCH RFC v3 3/3] mhsld: implement MHSLD device
Date: Fri, 24 Jan 2025 10:50:53 -0500 [thread overview]
Message-ID: <Z5O23R434TcP0fMo@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20250124141246.000040b0@huawei.com>
On Fri, Jan 24, 2025 at 02:12:46PM +0000, Jonathan Cameron wrote:
> On Fri, 18 Oct 2024 12:12:52 -0400
> Gregory Price <gourry@gourry.net> wrote:
>
> > From: Svetly Todorov <svetly.todorov@memverge.com>
> >
> > Using a shared-memory bytemap, validates that DC adds, releases,
> > and reclamations happen on extents belonging to the appropriate
> > host.
> >
> I'll carry this on my staging tree for now gitlab.com/jic23/qemu (latest date branch).
> I'll push out a bit later today.
> Few rebase related changes were needed. I've not tested it yet.
>
> Also I have dropped the previous prototype device Niagara on basis this
> should give people a better platform to work with.
>
Agreed. Niagara was a good step to get here.
Let me know how I can help.
~Gregory
prev parent reply other threads:[~2025-01-24 15:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 16:12 [PATCH RFC v3 0/3] cxl: Multi-headed Single Logical Device (MHSLD) Gregory Price
2024-10-18 16:12 ` [PATCH RFC v3 1/3] cxl-mailbox-utils: move CXLUpdateDCExtentListInPl into header Gregory Price
2024-10-18 16:12 ` [PATCH RFC v3 2/3] cxl_type3: add MHD callbacks Gregory Price
2024-12-12 17:12 ` Jonathan Cameron
2024-10-18 16:12 ` [PATCH RFC v3 3/3] mhsld: implement MHSLD device Gregory Price
2024-12-12 17:40 ` Jonathan Cameron
2024-12-12 19:52 ` Gregory Price
2024-12-13 16:18 ` Jonathan Cameron
2024-12-13 17:03 ` Gregory Price
2025-01-24 14:12 ` Jonathan Cameron
2025-01-24 15:50 ` Gregory Price [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=Z5O23R434TcP0fMo@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nifan.cxl@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=svetly.todorov@memverge.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