From: "Du, Changbin" <changbin.du@intel.com>
To: linux-pci@vger.kernel.org
Cc: changbin.du@intel.com, linux-kernel@vger.kernel.org
Subject: [Q] What about PCI mmio access alignment?
Date: Thu, 25 May 2017 18:12:57 +0800 [thread overview]
Message-ID: <20170525101256.GA12183@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Hi, guys,
I have a basic quesion about the alignment when access PCI bar mmio space. Is
the address accessed must be DW aligned and count must be DW aligned?
As far as I know, The address field of TLB ignore lower 2 bits and the unit of
length field also is DW. So does it mean above question is Yes? Else will CPU
handle unaligned access for mmio space?
I want to know wether below access illegal or not:
- readb(bar0)
- readb(bar0 + 1)
- readl(bar0)
Thanks,
Changbin Du
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2017-05-25 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 10:12 Du, Changbin [this message]
2017-05-27 15:32 ` [Q] What about PCI mmio access alignment? Andy Shevchenko
2017-05-28 10:54 ` Du, Changbin
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=20170525101256.GA12183@intel.com \
--to=changbin.du@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.