linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ismael Luceno Cortes <ismael.luceno@silicon-gears.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Patrik Niklasson <patrik.niklasson@silicon-gears.com>
Subject: Re: Exploring the PCI EP Framework
Date: Wed, 13 Nov 2019 14:47:42 +0000	[thread overview]
Message-ID: <20191113144742.GA2680@kiki> (raw)
In-Reply-To: <6e534239-36c7-086f-502a-fa399917f5f7@ti.com>

I'm adding Patrik, who was interested in the thread.

On 13/Nov/2019 15:36, Kishon Vijay Abraham I wrote:
<...> 
> The endpoint relies on polling a shared memory to detect any events. However if
> the HW supports some sort of memory signaled interrupt (similar to what is
> usually available in systems with RC) then we could use it for interrupting the
> endpoint system. All we have to do is map the MSI address to a EP BAR region so
> that host can write to a mapped BAR in order to raise MSI interrupt.

I was proposing exactly that internally here, but I'm not 100% happy
with having the RC-side driver trigger the interrupts this way as we
need to expose a hint about "how", but it's probably the only safe bet
(we know the endpoints in question will always support MSI-X).

> Even if the HW supports, the EP framework doesn't support to use MSI. I'll have
> to see how that can be added.

Thanks for the confirmation. Where's the polling happening? I can take a
look at that.

Patrik: Can you check if we could publish that part of our docs? It
would involve only the signalling.

> > I realize it may not exist because it would imply not yet existing
> > mechanisms. I even don't know if such a thing is feasible with a
> > standard IOMMU, but I'm trying to figure out just that.
> 
> Does the PCI EP controller also wired to IOMMU?

No, I'm just daydreaming: a programmable IOMMU could implement magic
pages which produce rewrites, hooked to the PPR mechanics. Even if it's
not all hardwired, I don't think I could get to play with that.

> > I'm tempted to try to glue together the EP framework with VFIO for the
> > purpose.
> 
> That would help to create a user space endpoint function driver. Not sure if
> it'll help for the doorbell.

Oh, now that I read it again, it's confusing, I meant I would like to
tie EP Framework with VFIO somehow, to implement the EPFs in user-space;
completely unrelated to the previous comments.

> > 
> > Are you aware of any efforts along those lines?
> 
> Most of the efforts in EP right now are towards binding the epf to virtio.
> https://lore.kernel.org/linux-pci/20190905161516.2845-1-haotian.wang@sifive.com/T/#m4092f14a49852425a00a9a9afa80b4d3b1b836d1

Very interesting, I didn't hit any limitations because our EPC driver is
a hack, but we're going to go with the EP Framework in the end, so good
to know (plus we're using virtio already in pretty much the same way).

Thank you very much.

Best regards.

-- 
Ismael Luceno <ismael.luceno@silicon-gears.com>
+34 934452260 ext. 139
Travessera de les Corts 302 Bajos, 08029 Barcelona, Spain

https://www.silicon-gears.com/ - https://www.tttech-auto.com/

      reply	other threads:[~2019-11-13 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191112114854.GA3478@kiki>
2019-11-13 10:06 ` Exploring the PCI EP Framework Kishon Vijay Abraham I
2019-11-13 14:47   ` Ismael Luceno Cortes [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=20191113144742.GA2680@kiki \
    --to=ismael.luceno@silicon-gears.com \
    --cc=kishon@ti.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=patrik.niklasson@silicon-gears.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;
as well as URLs for NNTP newsgroup(s).