From: Yan Zhao <yan.y.zhao@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: <kraxel@redhat.com>, <maarten.lankhorst@linux.intel.com>,
<mripard@kernel.org>, <airlied@gmail.com>, <daniel@ffwll.ch>,
<virtualization@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<pbonzini@redhat.com>, <seanjc@google.com>, <kvm@vger.kernel.org>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH] drm/bochs: use ioremap_wc() to map framebuffer during driver probing
Date: Mon, 9 Sep 2024 21:19:12 +0800 [thread overview]
Message-ID: <Zt710MSzAAcVEw0n@yzhao56-desk.sh.intel.com> (raw)
In-Reply-To: <78cf5ef4-09a1-4f7e-ab88-cbffdd967af3@suse.de>
On Mon, Sep 09, 2024 at 08:40:30AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 09.09.24 um 07:15 schrieb Yan Zhao:
> > Use ioremap_wc() instead of ioremap() to map framebuffer during driver
> > probing phase.
> >
> > Using ioremap() results in a VA being mapped with PAT=UC-. Additionally,
> > on x86 architectures, ioremap() invokes memtype_reserve() to reserve the
> > memory type as UC- for the physical range. This reservation can cause
> > subsequent calls to ioremap_wc() to fail to map the VA with PAT=WC to the
> > same physical range for framebuffre in ttm_kmap_iter_linear_io_init().
> > Consequently, the operation drm_gem_vram_bo_driver_move() ->
> > ttm_bo_move_memcpy() -> ttm_move_memcpy() becomes significantly slow on
> > platforms where UC memory access is slow.
>
> I've noticed this too and pushed a major update that replaces the entire
> memory management. [1]
>
> The patch is still welcome, I think, but you may want to rebase onto the
> latest drm-misc-next branch. [2]
>
> Best regards
> Thomas
>
> [1] https://patchwork.freedesktop.org/series/138086/
> [2] https://gitlab.freedesktop.org/drm/misc/kernel/-/tree/drm-misc-next
Thanks!
The updated version is at
https://lore.kernel.org/all/20240909131643.28915-1-yan.y.zhao@intel.com
prev parent reply other threads:[~2024-09-09 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 5:15 Yan Zhao
2024-09-09 6:40 ` Thomas Zimmermann
2024-09-09 13:19 ` Yan Zhao [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=Zt710MSzAAcVEw0n@yzhao56-desk.sh.intel.com \
--to=yan.y.zhao@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=vkuznets@redhat.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
all inboxes | Powered by JetHome®