From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com
Subject: Re: IO space memcpy support for userspace.
Date: Sat, 6 Dec 2008 11:07:54 -0500 [thread overview]
Message-ID: <119aab440812060807i8ca0583pdf9aa3b15bdc54fd@mail.gmail.com> (raw)
In-Reply-To: <21d7e9970812052234u58586957y83d618eea295e0f7@mail.gmail.com>
On Sat, Dec 6, 2008 at 1:34 AM, Dave Airlie <airlied@gmail.com> wrote:
> Its a real pain in the ass with dynamic buffer objects, we don't want userspace
> to care where they are located, the kernel migrates them in/out of
> video memory, GART, local RAM etc.
>
> However I suspect I just need on these platforms to ban any CPU
> accesses to pixmaps in VRAM. However
> sw fallbacks to the front buffer will always need these accesses.
>
> Its going to be a real pain getting any traction this stuff upstream
> (X.org/Mesa) where the world is x86 and maybe the odd powerpc, having
> to do special accessors for shithouse hw is never going to be fun.
Is there no case on x86 when this matters?
What about ARM, ColdFire or MIPS?
As the embedded market continues to grow I hope to see X.org/Mesa on
more hardware with different memory access rules.
Cheers,
Carlos.
next prev parent reply other threads:[~2008-12-06 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 3:40 Dave Airlie
2008-12-05 17:32 ` Carlos O'Donell
2008-12-05 20:22 ` David Miller
2008-12-06 6:34 ` Dave Airlie
2008-12-06 16:07 ` Carlos O'Donell [this message]
2008-12-08 5:24 ` Robert Hancock
2008-12-05 20:27 ` Roland McGrath
2008-12-06 6:30 ` Dave Airlie
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=119aab440812060807i8ca0583pdf9aa3b15bdc54fd@mail.gmail.com \
--to=carlos@systemhalted.org \
--cc=airlied@gmail.com \
--cc=davem@davemloft.net \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@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 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®