From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Rob Clark <robdclark@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: GEM allocation for para-virtualized DRM driver
Date: Sat, 18 Mar 2017 16:56:00 +0200 [thread overview]
Message-ID: <7f2360da-737b-79bb-109f-4c3071254edb@gmail.com> (raw)
In-Reply-To: <CAF6AEGtSdys7o_s6w9TUPuBPLdKjmZTHqev1SFweYSv27Zmw4g@mail.gmail.com>
On 03/18/2017 04:50 PM, Rob Clark wrote:
> On Sat, Mar 18, 2017 at 10:44 AM, Oleksandr Andrushchenko
> <andr2000@gmail.com> wrote:
>>>>> then TTM might be useful.
>>>> I was looking into it, but it seems to be an overkill in my case
>>>> And isn't it that GEM should be used for new drivers, not TTM?
>>> Not really, it's just that (other than amdgpu which uses TTM) all of
>>> the newer drivers have been unified memory.
>> Good to know, thank you
>>> A driver for a new GPU
>>> that had vram of some sort should still use TTM.
>> our virtual GPU support is done on hypervisor level, so no changes to
>> existing GPU drivers. So, the only thing to care about is that the
>> buffers our DRM driver provides can be imported and used by that GPU
>> (there are other issues related to memory, e.g. if real GPU/firware can
>> see the memory of the guest, but this is another story)
>
> jfwiw, it might be useful to have a look at the intel GVT stuff.. they
> have recently (4.10) added para-virt support to i915
hm, thank you, I'll have a look at it (what is more when
I'm not using ARM I'm playing with x86+i915, so it can be handy)
> BR,
> -R
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-18 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 17:39 GEM allocation for para-virtualized DRM driver Oleksandr Andrushchenko
2017-03-18 12:22 ` Rob Clark
2017-03-18 13:25 ` Oleksandr Andrushchenko
2017-03-18 14:06 ` Rob Clark
2017-03-18 14:44 ` Oleksandr Andrushchenko
2017-03-18 14:50 ` Rob Clark
2017-03-18 14:56 ` Oleksandr Andrushchenko [this message]
2017-03-20 17:18 ` Oleksandr Andrushchenko
2017-03-20 17:38 ` Rob Clark
2017-03-20 18:01 ` Oleksandr Andrushchenko
2017-03-20 18:17 ` Rob Clark
2017-03-20 18:25 ` Oleksandr Andrushchenko
2017-03-20 18:52 ` Rob Clark
2017-03-20 19:05 ` Oleksandr Andrushchenko
2017-03-21 15:12 ` Oleksandr Andrushchenko
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=7f2360da-737b-79bb-109f-4c3071254edb@gmail.com \
--to=andr2000@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.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 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.