From: "Piórkowski, Piotr" <piotr.piorkowski@intel.com>
To: <igt-dev@lists.freedesktop.org>
Cc: "Piotr Piórkowski" <piotr.piorkowski@intel.com>,
"Lukasz Laguna" <lukasz.laguna@intel.com>
Subject: [PATCH i-g-t,v3 1/2] lib/intel_mmio: Map the whole BAR0 for gen12+
Date: Wed, 3 Apr 2024 14:09:54 +0200 [thread overview]
Message-ID: <20240403120955.4070545-2-piotr.piorkowski@intel.com> (raw)
In-Reply-To: <20240403120955.4070545-1-piotr.piorkowski@intel.com>
From: Piotr Piórkowski <piotr.piorkowski@intel.com>
Previously, we limited BAR0 mapping to register space only because of
the potential conflict with wc mapping for the GTT region.
For gen12+ platforms, the size of BAR0 varies due to the different amount
of tile.
And as for gen11+ platforms, we can already map the whole BAR0 as uc,
so let's map the whole BAR0, without artificial limitations.
Signed-off-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
Reviewed-by: Lukasz Laguna <lukasz.laguna@intel.com>
---
lib/intel_mmio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/intel_mmio.c b/lib/intel_mmio.c
index 4b6820787..31975727e 100644
--- a/lib/intel_mmio.c
+++ b/lib/intel_mmio.c
@@ -154,7 +154,7 @@ intel_mmio_use_pci_bar(struct intel_mmio_data *mmio_data, struct pci_device *pci
gen = intel_gen(devid);
if (gen >= 12)
- mmio_size = 8 * 1024 * 1024;
+ mmio_size = pci_dev->regions[mmio_bar].size;
else if (gen >= 5)
mmio_size = 2 * 1024 * 1024;
else
--
2.34.1
next prev parent reply other threads:[~2024-04-03 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:09 [PATCH i-g-t,v3 0/2] lib/xe_mmio: Introduce Xe MMIO lib Piórkowski, Piotr
2024-04-03 12:09 ` Piórkowski, Piotr [this message]
2024-04-03 12:09 ` [PATCH i-g-t,v3 2/2] " Piórkowski, Piotr
2024-04-05 8:17 ` Laguna, Lukasz
2024-04-04 7:40 ` ✗ Fi.CI.BAT: failure for lib/xe_mmio: Introduce Xe MMIO lib (rev3) Patchwork
2024-04-05 10:21 ` Piotr Piórkowski
2024-04-04 7:56 ` ✓ CI.xeBAT: success " Patchwork
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=20240403120955.4070545-2-piotr.piorkowski@intel.com \
--to=piotr.piorkowski@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lukasz.laguna@intel.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