From: Davidlohr Bueso <dave@stgolabs.net>
To: Gregory Price <gregory.price@memverge.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Gregory Price <gourry.memverge@gmail.com>,
qemu-devel@nongnu.org, linux-cxl@vger.kernel.org,
Alison Schofield <alison.schofield@intel.com>,
"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: Fri, 7 Oct 2022 12:55:00 -0700 [thread overview]
Message-ID: <20221007195500.37tpbrl533qmtng2@offworld> (raw)
In-Reply-To: <Y0Bz7OrSxBYNGfNR@memverge.com>
On Fri, 07 Oct 2022, Gregory Price wrote:
>Spec says that volatile devices `may` implement an lsa.
Right you are.
>Get LSA (Opcode 4102h)
>The Label Storage Area (LSA) shall be supported by a memory device
>that provides persistent memory capacity and may be supported by a
>device that provides only volatile memory capacity. The format of
>the LSA is specified in Section 9.13.2. The size of the Label Storage
>Area is retrieved from the Identify Memory Device command.
next prev parent reply other threads:[~2022-10-07 20:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 0:01 [PATCH RFC] hw/cxl: type 3 devices can now present volatile or persistent memory Gourry
2022-10-06 8:45 ` Jonathan Cameron via
2022-10-06 8:50 ` Jonathan Cameron via
2022-10-06 15:52 ` Gregory Price
2022-10-06 16:42 ` Jonathan Cameron via
2022-10-06 17:29 ` Gregory Price
2022-10-07 14:50 ` Gregory Price
2022-10-10 15:18 ` Jonathan Cameron via
2022-10-10 15:25 ` Gregory Price
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 via
2022-10-10 14:43 ` Jonathan Cameron via
2022-10-10 15:20 ` Gregory Price
2022-10-10 16:26 ` Jonathan Cameron via
2022-10-10 16:32 ` Jonathan Cameron via
2022-10-10 17:18 ` Davidlohr Bueso
2022-10-07 18:16 ` Davidlohr Bueso
2022-10-07 18:46 ` Gregory Price
2022-10-07 19:55 ` Davidlohr Bueso [this message]
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=20221007195500.37tpbrl533qmtng2@offworld \
--to=dave@stgolabs.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=gourry.memverge@gmail.com \
--cc=gregory.price@memverge.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;
as well as URLs for NNTP newsgroup(s).