linux-kernel - Re: [PATCH v7 09/16] libnvdimm, pmem: move pmem to drivers/nvdimm/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPcyv4j-anyF1Tt3F5G7yoQpfik9SmhXEojUmSrPm+SMVN31Sw@mail.gmail.com>
Date:	Wed, 1 Jul 2015 10:24:53 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
	Jens Axboe <axboe@...nel.dk>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Neil Brown <neilb@...e.de>,
	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Jeff Moyer <jmoyer@...hat.com>,
	"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v7 09/16] libnvdimm, pmem: move pmem to drivers/nvdimm/

On Wed, Jul 1, 2015 at 9:49 AM, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> On Wed, Jul 1, 2015 at 6:41 PM, Dan Williams <dan.j.williams@...el.com> wrote:
>> On Wed, Jul 1, 2015 at 6:13 AM, Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>>> On Thu, Jun 18, 2015 at 1:14 AM, Dan Williams <dan.j.williams@...el.com> wrote:
>>>> Prepare the pmem driver to consume PMEM namespaces emitted by regions of
>>>> an nvdimm_bus instance.  No functional change.
>>>
>>> As LIBNVDIMM depends on PHYS_ADDR_T_64BIT, the driver can no
>>> longer be enabled on pure 32-bit platforms. Is that intended?
>>
>> Yes it was intentional.  It still allows 32-bit platforms with 64-bit
>> resource_size_t to compile. Do you otherwise have a 32-bit use case
>> for pmem?  I'm of course open to working through the changes to add
>> wider architecture support.
>
> Nope, just wondering, as the original didn't depend on PHYS_ADDR_T_64BIT.

Not explicitly, but it did rely on X86_PMEM_LEGACY.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/