From: Gregory Price <gregory.price@memverge.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Gregory Price <gourry.memverge@gmail.com>,
qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
Alison Schofield <alison.schofield@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
"a.manzanares@samsung.com" <a.manzanares@samsung.com>,
Ben Widawsky <bwidawsk@kernel.org>
Subject: Re: [PATCH RFC] hw/cxl: type 3 devices can now present volatile or persistent memory
Date: Mon, 10 Oct 2022 11:25:31 -0400 [thread overview]
Message-ID: <Y0Q5a2Wx3qFB2eKI@memverge.com> (raw)
In-Reply-To: <20221010161809.00006f8e@huawei.com>
>
> https://gitlab.com/jic23/qemu/-/commits/cxl-2022-10-09
> There are a few messy corners in that tree but it should work. I'll be
> pushing out a new version in a few days.
>
> I updated that in latest version to build the tables based on the
> memdev provided. We'll want to add the volatile support to that alongside
> your patch.
>
I will rebase my --persistent-memdev and --volatile-memdev patch on your
branch and send out the commits when i'm done. I may also add the
scafolding for the partitionable-pmem field but not actually expose it.
next prev parent reply other threads:[~2022-10-10 15:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221006000103.49542-1-gregory.price@memverge.com>
2022-10-06 8:45 ` [PATCH RFC] hw/cxl: type 3 devices can now present volatile or persistent memory Jonathan Cameron
2022-10-06 8:50 ` Jonathan Cameron
2022-10-06 15:52 ` Gregory Price
2022-10-06 16:42 ` Jonathan Cameron
2022-10-06 17:29 ` Gregory Price
2022-10-10 14:43 ` Jonathan Cameron
2022-10-10 15:20 ` Gregory Price
2022-10-10 16:26 ` Jonathan Cameron
2022-10-10 16:32 ` Jonathan Cameron
2022-10-10 17:18 ` Davidlohr Bueso
[not found] ` <CAD3UvdT1ZHJDaqj05C+n7t4rM7yhjZyM6fooXAfG12rAYnBqmw@mail.gmail.com>
2022-10-10 15:18 ` Jonathan Cameron
2022-10-10 15:25 ` Gregory Price [this message]
2022-10-11 1:23 ` Gregory Price
2022-10-11 17:14 ` Davidlohr Bueso
2022-10-11 17:22 ` Gregory Price
2022-10-11 17:28 ` Jonathan Cameron
2022-10-07 18:16 ` Davidlohr Bueso
2022-10-07 18:46 ` Gregory Price
2022-10-07 19:55 ` Davidlohr Bueso
2022-10-07 19:52 ` Davidlohr Bueso
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=Y0Q5a2Wx3qFB2eKI@memverge.com \
--to=gregory.price@memverge.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dave@stgolabs.net \
--cc=gourry.memverge@gmail.com \
--cc=linux-cxl@vger.kernel.org \
--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