Linux PCI subsystem development
 help / color / mirror / Atom feed
From: nowicki@posteo.net
To: linux-pci@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: [Question] Custom MMIO handler - is it possible?
Date: Wed, 31 Jan 2024 20:42:18 +0000	[thread overview]
Message-ID: <981728318a564e6c3d54ca76ee37348b@posteo.net> (raw)

Hello,

I'm trying to implement a fake PCIe device and I'm looking for guidance 
(by fake I mean fully software device).

So far I implemented:
- fake PCIe bus with custom fake pci_ops.read & pci_ops.write functions
- fake PCIe switch
- fake PCIe endpoint

Fake devices have implemented PCIe registers and are visible in user 
space via lspci tool.
Registers can be edited via setpci tool.

Now I'm looking for a way to implement BAR regions with custom memory 
handlers. Is it even possible?
Basically I'd like to capture each MemoryWrite & MemoryRead targeted for 
PCIe endpoint's BAR region and emulate NVMe registers.

I'm in dead-end right now and I'm seeing only two options:
- generate page faults on every access to fake BAR region and execute 
fake PCIe endpoint's callbacks - similar/the same as mmiotrace
- periodically scan fake BAR region for any changes

Both solutions have drawbacks.
Is there other way to implement fake BAR region?


Regards,
Mateusz

             reply	other threads:[~2024-01-31 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 20:42 nowicki [this message]
2024-01-31 21:20 ` [Question] Custom MMIO handler - is it possible? Bjorn Helgaas
2024-02-01 15:38   ` Mateusz Nowicki
2024-02-01 18:06     ` Bjorn Helgaas

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=981728318a564e6c3d54ca76ee37348b@posteo.net \
    --to=nowicki@posteo.net \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-pci@vger.kernel.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