All of lore.kernel.org
 help / color / mirror / Atom feed
From: Your name <nobelkernel@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: PCI: PCIe endpoint initiating write request to RC
Date: Wed, 16 Sep 2015 12:23:40 +0530	[thread overview]
Message-ID: <20150916065338.GA24779@gmail.com> (raw)

Hi,

I have a doubt, hope some one would have come across the same,

For a root complex to send data to PCIe endpoints, Then it has to write data
that could hit the BAR region of PCIe endpoints.

For a vice versa, if PCIe endpoint which doesn't has DMA descriptor in it and
it is trying to send data. which address I need to configure? Any
physical address of ram or physical address got for kmalloc or endpoint BAR? 

If PCIe endpoint can access the entire memory does it has a permission to
corrupt the host memory from external. We know linux handle memory
violation for process by memory structure assigned in each task_struct.
But can someone explain me how it been managed for data comming out from
endpoint to Root complex?

Regards
Nobel

                 reply	other threads:[~2015-09-16  6:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150916065338.GA24779@gmail.com \
    --to=nobelkernel@gmail.com \
    --cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.