From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 1/5] drm/i915: Round up object allocations
Date: Sat, 25 Jan 2014 21:49:57 -0800 [thread overview]
Message-ID: <20140126054957.GA1926@bwidawsk.net> (raw)
In-Reply-To: <20140125202824.GM9772@phenom.ffwll.local>
On Sat, Jan 25, 2014 at 09:28:24PM +0100, Daniel Vetter wrote:
> On Thu, Jan 23, 2014 at 07:21:10PM -0800, Ben Widawsky wrote:
> > DRM gets very mad when you request an object which occupies a partial
> > page. As a DRM driver, i915 never really wants to anger DRM, and would
> > always just want the rounding done for us.
> >
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > ---
> > drivers/gpu/drm/i915/i915_gem.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> > index 024e454..8cd1134 100644
> > --- a/drivers/gpu/drm/i915/i915_gem.c
> > +++ b/drivers/gpu/drm/i915/i915_gem.c
> > @@ -4168,6 +4168,8 @@ struct drm_i915_gem_object *i915_gem_alloc_object(struct drm_device *dev,
> > struct address_space *mapping;
> > gfp_t mask;
> >
> > + size = round_up(size, PAGE_SIZE);
> > +
>
> Nope, if there's some code that doesn't do page-aligend bo allocations it
> needs to be fixed there. If you want throw a WARN_ON and early return in
> here.
> -Daniel
Why?
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-01-26 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1390533674-18402-1-git-send-email-benjamin.widawsky@intel.com>
2014-01-24 3:21 ` [PATCH 1/5] drm/i915: Round up object allocations Ben Widawsky
2014-01-25 20:28 ` Daniel Vetter
2014-01-26 5:49 ` Ben Widawsky [this message]
2014-01-26 9:17 ` Daniel Vetter
2014-01-26 9:57 ` Chris Wilson
2014-01-26 10:01 ` Daniel Vetter
2014-01-26 10:07 ` Chris Wilson
2014-01-26 19:00 ` Ben Widawsky
2014-01-26 19:59 ` Daniel Vetter
2014-01-26 20:03 ` Chris Wilson
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=20140126054957.GA1926@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 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.