Cc: Dan Williams
Cc: Vishal Verma
Cc: Ira Weiny
Cc: Alison Schofield
Signed-off-by: Ben Widawsky
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6eff4f720c72..93c8694a8f04 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -,6
It's often useful in debug scenarios to see what the hardware has dumped
out. As it stands today, any device error will result in the payload not
being copied out, so there is no way to triage commands which weren't
expected to fail (and sometimes the payload may have that information).
The
Title: Dear
Dear Sir/Ma,
$150 MILLION USD FROM WORLD HEALTH ORGANIZATION DIVERTED AND READY TO BE
CLAIMED.
Greetings to you and happy new year 2021. Please take few minutes of your time
to read this.
My name is Mr. Anthony Ray Chavis from North Carolina USA, I Currently work with
the
Add initial set of formal commands beyond basic identify and command
enumeration.
Signed-off-by: Ben Widawsky
Reviewed-by: Dan Williams
Reviewed-by: Jonathan Cameron (v2)
---
drivers/cxl/mem.c| 9 +
include/uapi/linux/cxl_mem.h | 5 +
2 files changed, 14 insertions(+)
CXL devices identified by the memory-device class code must implement
the Device Command Interface (described in 8.2.9 of the CXL 2.0 spec).
While the driver already maintains a list of commands it supports, there
is still a need to be able to distinguish between commands that the
driver knows
The CXL memory device send interface will have a number of supported
commands. The raw command is not such a command. Raw commands allow
userspace to send a specified opcode to the underlying hardware and
bypass all driver checks on the command. The primary use for this
command is to
Add a straightforward IOCTL that provides a mechanism for userspace to
query the supported memory device commands. CXL commands as they appear
to userspace are described as part of the UAPI kerneldoc. The command
list returned via this IOCTL will contain the full set of commands that
the driver
From: Dan Williams
Create the /sys/bus/cxl hierarchy to enumerate:
* Memory Devices (per-endpoint control devices)
* Memory Address Space Devices (platform address ranges with
interleaving, performance, and persistence attributes)
* Memory Regions (active provisioned memory from an address
Provide enough functionality to utilize the mailbox of a memory device.
The mailbox is used to interact with the firmware running on the memory
device. The flow is proven with one implemented command, "identify".
Because the class code has already told the driver this is a memory
device and the
From: Dan Williams
The CXL.mem protocol allows a device to act as a provider of "System
RAM" and/or "Persistent Memory" that is fully coherent as if the memory
was attached to the typical CPU memory controller.
With the CXL-2.0 specification a PCI endpoint can implement a "Type-3"
device
# Changes since v2 [1]
* s/mbox_lock/mbox_mutex in kdocs (Ben)
* Remove stray comments about deleted flags (Ben)
* Remove flags from CXL_CMD (Ben)
* Rework cxl_mem_enumerate_cmds() to allow more than 2 commands (Ben,
Jonathan)
* I misread the spec and this needed more robust
nvdimm_remove is only ever called after nvdimm_probe() returned
successfully. In this case driver data is always set to a non-NULL value
so the check for driver data being NULL can go away as it's always false.
Signed-off-by: Uwe Kleine-König
---
drivers/nvdimm/dimm.c | 3 ---
1 file changed, 3
All drivers return 0 in their remove callback and the driver core ignores
the return value of nvdimm_bus_remove() anyhow. So simplify by changing
the driver remove callback to return void and return 0 unconditionally
to the upper layer.
Signed-off-by: Uwe Kleine-König
---
On 21-02-12 13:27:06, Jonathan Cameron wrote:
> On Thu, 11 Feb 2021 07:55:29 -0800
> Ben Widawsky wrote:
>
> > On 21-02-11 09:55:48, Jonathan Cameron wrote:
> > > On Wed, 10 Feb 2021 10:16:05 -0800
> > > Ben Widawsky wrote:
> > >
> > > > On 21-02-10 08:55:57, Ben Widawsky wrote:
> > > > >
On Thu, 11 Feb 2021 08:01:48 -0800
Ben Widawsky wrote:
> On 21-02-11 11:19:24, Jonathan Cameron wrote:
> > On Tue, 9 Feb 2021 16:02:56 -0800
> > Ben Widawsky wrote:
> >
> > > The CXL memory device send interface will have a number of supported
> > > commands. The raw command is not such a
On Thu, 11 Feb 2021 12:40:45 -0800
Dan Williams wrote:
> On Thu, Feb 11, 2021 at 2:19 AM Jonathan Cameron
> wrote:
> >
> > On Wed, 10 Feb 2021 18:17:25 +
> > Jonathan Cameron wrote:
> >
> > > On Tue, 9 Feb 2021 16:02:54 -0800
> > > Ben Widawsky wrote:
> > >
> > > > From: Dan Williams
On Thu, 11 Feb 2021 07:55:29 -0800
Ben Widawsky wrote:
> On 21-02-11 09:55:48, Jonathan Cameron wrote:
> > On Wed, 10 Feb 2021 10:16:05 -0800
> > Ben Widawsky wrote:
> >
> > > On 21-02-10 08:55:57, Ben Widawsky wrote:
> > > > On 21-02-10 15:07:59, Jonathan Cameron wrote:
> > > > > On
On Thu, 11 Feb 2021 10:27:41 -0800
Ben Widawsky wrote:
> On 21-02-11 09:55:48, Jonathan Cameron wrote:
> > On Wed, 10 Feb 2021 10:16:05 -0800
> > Ben Widawsky wrote:
> >
> > > On 21-02-10 08:55:57, Ben Widawsky wrote:
> > > > On 21-02-10 15:07:59, Jonathan Cameron wrote:
> > > > > On
On Fri 12-02-21 00:59:29, Mike Rapoport wrote:
> On Thu, Feb 11, 2021 at 01:30:42PM +0100, Michal Hocko wrote:
[...]
> > Have a look how hugetlb proliferates through our MM APIs. I strongly
> > suspect this is strong signal that this won't be any different.
> >
> > > And even if yes, adding
On 12.02.21 00:09, Mike Rapoport wrote:
On Thu, Feb 11, 2021 at 01:07:10PM +0100, David Hildenbrand wrote:
On 11.02.21 12:27, Mike Rapoport wrote:
On Thu, Feb 11, 2021 at 10:01:32AM +0100, David Hildenbrand wrote:
So let's talk about the main user-visible differences to other memfd files
20 matches
Mail list logo
