linux-kernel - Re: [PATCH] [AGPGART] intel_agp: fix stolen mem range on G33

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0709110907240.11816@skynet.skynet.ie>
Date:	Tue, 11 Sep 2007 09:08:08 +0100 (IST)
From:	Dave Airlie <airlied@...ux.ie>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Zhenyu Wang <zhenyu.z.wang@...el.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [AGPGART] intel_agp: fix stolen mem range on G33

>>
>> Subject: [PATCH] [AGPGART] intel_agp: fix stolen mem range on G33
>>
>> G33 GTT stolen memory is below graphics data
>> stolen memory and be seperate, so don't subtract
>> it in stolen mem counting.
>>
>> Signed-off-by: Zhenyu Wang <zhenyu.z.wang@...el.com>

Andrew I meant to upstream these for 2.6.23 but travelling is still in 
progress, so if you could send them to Linus...

Acked-by: Dave Airlie <airlied@...ux.ie>


>> ---
>>  drivers/char/agp/intel-agp.c |    5 +++++
>>  1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
>> index 2c9ca2c..581f922 100644
>> --- a/drivers/char/agp/intel-agp.c
>> +++ b/drivers/char/agp/intel-agp.c
>> @@ -506,6 +506,11 @@ static void intel_i830_init_gtt_entries(void)
>>  			break;
>>  		}
>>  	} else {
>> +		/* G33's GTT stolen memory is separate from gfx data
>> +		 * stolen memory.
>> +		 */
>> +		if (IS_G33)
>> +			size = 0;
>>  		switch (gmch_ctrl & I830_GMCH_GMS_MASK) {
>>  		case I855_GMCH_GMS_STOLEN_1M:
>>  			gtt_entries = MB(1) - KB(size);
>
> When looking at a "fix" I need to work out whether it might be needed in
> 2.6.23.  But your description of this patch didn't describe the problem
> which it fixes in a way which allows me to decide this.
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/