Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Vijairaj <vijairaj.r@gmail.com>, linux-nvdimm@lists.01.org
Cc: Stephen Bates <Stephen.Bates@pmcs.com>
Subject: Re: Mapping PCIe BAR as PMEM
Date: Wed, 15 Jun 2016 18:31:00 -0600	[thread overview]
Message-ID: <5761F344.5060901@deltatee.com> (raw)
In-Reply-To: <CAJZPXDLcW3KYtxzJs=27b17bvisdv6g2MCj3fcJ9cU+YnQnwcQ@mail.gmail.com>

Hey Vijairaj,

This is essentially what we did with our iopmem work [1].

We wrote a PCI driver (see [2] for an example) and had a small patch to 
the kernel to enable mappings with write combining.

Logan

[1] http://www.spinics.net/lists/linux-mm/msg103990.html
[2] https://github.com/sbates130272/iopmem

On 15/06/16 07:57 AM, Vijairaj wrote:
> Hi,
> I am running the 4.4 kernel on AMD64 and was wondering what's a good way of
> mapping the 16M of battery backed SRAM on a custom PCIe card as PMEM. Once
> mapped, I will create a file system on the block device.
>
> I am thinking about doing the following:
>      - Use the kernel parameter memmap=nn!ss to reserve the PCIe BAR
>      - Write a PCI driver to enable the PCI device `pci_enable_device()`
>      - Load the PCI driver
>      - Load the nd_pmem driver
>
> Is this sufficient or is there anything else required to be done in the PCI
> driver?
>
> thanks,
> Vijairaj
> _______________________________________________
> Linux-nvdimm mailing list
> Linux-nvdimm@lists.01.org
> https://lists.01.org/mailman/listinfo/linux-nvdimm
>
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      parent reply	other threads:[~2016-06-16  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 13:57 Mapping PCIe BAR as PMEM Vijairaj
2016-06-15 14:33 ` Dan Williams
2016-06-16  0:31 ` Logan Gunthorpe [this message]

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=5761F344.5060901@deltatee.com \
    --to=logang@deltatee.com \
    --cc=Stephen.Bates@pmcs.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vijairaj.r@gmail.com \
    /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