All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
	Intel graphics driver community testing & development
	<intel-gfx@lists.freedesktop.org>,
	x86@kernel.org, Matthew Auld <matthew.auld@intel.com>,
	"H . Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit
Date: Fri, 24 Nov 2017 15:55:25 +0200	[thread overview]
Message-ID: <20171124135525.GI10981@intel.com> (raw)
In-Reply-To: <20171124073017.22212-1-joonas.lahtinen@linux.intel.com>

On Fri, Nov 24, 2017 at 09:30:17AM +0200, Joonas Lahtinen wrote:
> @@ -426,14 +426,14 @@ static size_t __init chv_stolen_size(int num, int slot, int func)
>  	 * 0x17 to 0x1d: 4MB increments start at 36MB
>  	 */
>  	if (gms < 0x11)
> -		return (size_t)gms * MB(32);
> +		return gms * MB(32);
>  	else if (gms < 0x17)
> -		return (size_t)(gms - 0x11 + 2) * MB(4);
> +		return (gms - 0x11 + 2) * MB(4);
>  	else
> -		return (size_t)(gms - 0x17 + 9) * MB(4);
> +		return (gms - 0x17 + 9) * MB(4);

Unrelated random idea: Maybe someone could replace the
semi-magic looking +2,+9 etc. with just +MB(whatever)?

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-11-24 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24  7:30 [PATCH] x86/early-quirks: Extend Intel graphics stolen memory placement to 64bit Joonas Lahtinen
2017-11-24  7:35 ` Ingo Molnar
2017-11-24 10:58   ` Joonas Lahtinen
2017-11-24  7:50 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-11-24 12:36 ` [PATCH] " Chris Wilson
2017-11-24 13:55 ` Ville Syrjälä [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=20171124135525.GI10981@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=matthew.auld@intel.com \
    --cc=mingo@kernel.org \
    --cc=paulo.r.zanoni@intel.com \
    --cc=x86@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 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.