From: Thomas Zimmermann <tzimmermann@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel@lists.freedesktop.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
open list <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH v3 1/5] gem/vram: pin to vram in vmap
Date: Thu, 27 Jun 2019 17:54:50 +0200 [thread overview]
Message-ID: <bd472b0a-faec-c97f-39a6-ffd0bd8fdd78@suse.de> (raw)
In-Reply-To: <20190627151633.j3xf3lkihklb2wzh@sirius.home.kraxel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1018 bytes --]
Hi
Am 27.06.19 um 17:16 schrieb Gerd Hoffmann:
> Hi,
>
>> 1) Introduce a default_placement field in struct drm_gem_vram_helper
>> where this flag can be configured. I'd favor this option.
>
>> 2) Introduce a separate callback function for pinning to vram. The
>> driver would have to set the correct function pointers.
>
>> 3) Pin the fb console buffer manually from within the bochs driver.
>
> Hmm. Before calling drm_fbdev_generic_setup() the bo doesn't exist yet
> and when the function returns it is already vmapped and pinned I think.
>
> So (3) isn't easily doable. (1) looks best to me.
For my patches, it's OK to have to BO pinned to VRAM by default. As the
BO will be unmapped most of the time, I can change this flag at any time.
Best regards
Thomas
> cheers,
> Gerd
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Linux GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-27 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190627122348.5833-1-kraxel@redhat.com>
2019-06-27 12:23 ` Gerd Hoffmann
2019-06-27 14:37 ` Thomas Zimmermann
2019-06-27 15:16 ` Gerd Hoffmann
2019-06-27 15:54 ` Thomas Zimmermann [this message]
2019-06-27 15:59 ` Thomas Zimmermann
2019-06-27 12:23 ` [PATCH v3 2/5] drm/bochs: pass framebuffer to bochs_hw_setbase Gerd Hoffmann
2019-06-27 12:23 ` [PATCH v3 3/5] drm/bochs: drop yres_virtual from struct bochs_device Gerd Hoffmann
2019-06-27 12:23 ` [PATCH v3 4/5] drm/bochs: drop stride and bpp " Gerd Hoffmann
2019-06-27 12:23 ` [PATCH v3 5/5] drm/bochs: move bochs_hw_setformat() call Gerd Hoffmann
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=bd472b0a-faec-c97f-39a6-ffd0bd8fdd78@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
/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®