On Thu, May 28, 2015 at 1:51 PM, Linda Knippers wrote:
> On 5/28/2015 3:59 PM, Dan Williams wrote:
>> On Thu, May 28, 2015 at 11:36 AM, Toshi Kani wrote:
>>> On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani wrote:
> On Tue, 2015-04-28 at
On 5/28/2015 3:59 PM, Dan Williams wrote:
> On Thu, May 28, 2015 at 11:36 AM, Toshi Kani wrote:
>> On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
>>> On Mon, May 4, 2015 at 1:26 PM, Toshi Kani wrote:
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
>> :
The libnd
On Thu, May 28, 2015 at 11:36 AM, Toshi Kani wrote:
> On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
>> On Mon, May 4, 2015 at 1:26 PM, Toshi Kani wrote:
>> > On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
> :
>> >
>> > The libnd does not support memdev->flags, which contains
On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
> On Mon, May 4, 2015 at 1:26 PM, Toshi Kani wrote:
> > On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
> >
> > The libnd does not support memdev->flags, which contains "Memory Device
> > State Flags" defined in Table 5-129 of ACPI
On 5/28/2015 3:59 PM, Dan Williams wrote:
On Thu, May 28, 2015 at 11:36 AM, Toshi Kani toshi.k...@hp.com wrote:
On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani toshi.k...@hp.com wrote:
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
On Thu, May 28, 2015 at 11:36 AM, Toshi Kani toshi.k...@hp.com wrote:
On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani toshi.k...@hp.com wrote:
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
The libnd does not support
On Thu, May 28, 2015 at 1:51 PM, Linda Knippers linda.knipp...@hp.com wrote:
On 5/28/2015 3:59 PM, Dan Williams wrote:
On Thu, May 28, 2015 at 11:36 AM, Toshi Kani toshi.k...@hp.com wrote:
On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani
On Sat, 2015-05-09 at 16:55 -0700, Dan Williams wrote:
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani toshi.k...@hp.com wrote:
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
The libnd does not support memdev-flags, which contains Memory Device
State Flags defined in Table 5-129 of
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani wrote:
> On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
> :
>> +
>> +static int nd_acpi_register_region(struct acpi_nfit_desc *acpi_desc,
>> + struct nfit_spa *nfit_spa)
>> +{
>> + static struct nd_mapping
On Mon, May 4, 2015 at 1:26 PM, Toshi Kani toshi.k...@hp.com wrote:
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
+
+static int nd_acpi_register_region(struct acpi_nfit_desc *acpi_desc,
+ struct nfit_spa *nfit_spa)
+{
+ static struct nd_mapping
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
> +
> +static int nd_acpi_register_region(struct acpi_nfit_desc *acpi_desc,
> + struct nfit_spa *nfit_spa)
> +{
> + static struct nd_mapping nd_mappings[ND_MAX_MAPPINGS];
> + struct acpi_nfit_spa *spa = nfit_spa->spa;
>
On Tue, 2015-04-28 at 14:24 -0400, Dan Williams wrote:
:
+
+static int nd_acpi_register_region(struct acpi_nfit_desc *acpi_desc,
+ struct nfit_spa *nfit_spa)
+{
+ static struct nd_mapping nd_mappings[ND_MAX_MAPPINGS];
+ struct acpi_nfit_spa *spa = nfit_spa-spa;
+
PATCH v2 08/20] libnd, nd_acpi: regions (block-
>> data-window, persistent memory, volatile memory)
>>
>> A "region" device represents the maximum capacity of a BLK range (mmio
>> block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
>> vo
> -Original Message-
> From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of
> Dan Williams
> Sent: Tuesday, April 28, 2015 1:25 PM
> Subject: [Linux-nvdimm] [PATCH v2 08/20] libnd, nd_acpi: regions (block-
> data-window, persistent memor
, nd_acpi: regions (block-
data-window, persistent memory, volatile memory)
A region device represents the maximum capacity of a BLK range (mmio
block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
volatile memory), without regard for aliasing. Aliasing, in the
dimm-local
-Original Message-
From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of
Dan Williams
Sent: Tuesday, April 28, 2015 1:25 PM
Subject: [Linux-nvdimm] [PATCH v2 08/20] libnd, nd_acpi: regions (block-
data-window, persistent memory, volatile memory)
A region
A "region" device represents the maximum capacity of a BLK range (mmio
block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
volatile memory), without regard for aliasing. Aliasing, in the
dimm-local address space (DPA), is resolved by metadata on a dimm to
designate which
A region device represents the maximum capacity of a BLK range (mmio
block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
volatile memory), without regard for aliasing. Aliasing, in the
dimm-local address space (DPA), is resolved by metadata on a dimm to
designate which
18 matches
Mail list logo