public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@kernel.org>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH 4/4] x86, gart: Make sure GART does not map physmem above 1TB
Date: Wed, 20 Apr 2011 10:38:28 -0700	[thread overview]
Message-ID: <4DAF1A14.2090703@kernel.org> (raw)
In-Reply-To: <20110419142904.GT2192@amd.com>

On 04/19/2011 07:29 AM, Roedel, Joerg wrote:
>>
>> Arguably we call this the k8_nb in other places, so my suggestion would
>> be k8_gart.c
> 
> The k8_nb was renamed to amd_nb recently. The NB is implemented in all
> 64 bit AMD processors and there are more today then K8. The k8_nb was
> historically chosen and misleading today.
> 

OK, fair enough.  However, unless it is actually used in 32-bit mode
calling it amd_gart_64.c is probably better than amd64_gart.c since an
"amd64" processor can also be run in 32-bit mode.

	-hpa

  reply	other threads:[~2011-04-20 17:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 13:45 [PATCH 0/4] gart cleanups and fixes Joerg Roedel
2011-04-18 13:45 ` [PATCH 1/4] x86, gart: Don't enforce GART aperture lower-bound by alignment Joerg Roedel
2011-04-18 14:45   ` H. Peter Anvin
2011-04-18 14:56     ` Roedel, Joerg
2011-04-18 15:51       ` H. Peter Anvin
2011-04-18 17:36         ` Joerg Roedel
2011-04-18 17:39           ` H. Peter Anvin
2011-04-18 17:50             ` Joerg Roedel
2011-04-18 19:06             ` Joerg Roedel
2011-04-18 19:40               ` H. Peter Anvin
2011-04-18 18:29   ` Yinghai Lu
2011-04-18 18:39   ` [tip:x86/gart] " tip-bot for Joerg Roedel
2011-04-18 13:45 ` [PATCH 2/4] x86, gart: Convert spaces to tabs in enable_gart_translation Joerg Roedel
2011-04-18 16:39   ` [tip:x86/urgent] " tip-bot for Joerg Roedel
2011-04-18 13:45 ` [PATCH 3/4] x86, gart: Set DISTLBWALKPRB bit always Joerg Roedel
2011-04-18 16:40   ` [tip:x86/urgent] " tip-bot for Joerg Roedel
2011-04-18 13:45 ` [PATCH 4/4] x86, gart: Make sure GART does not map physmem above 1TB Joerg Roedel
2011-04-18 14:46   ` H. Peter Anvin
2011-04-18 14:52     ` Roedel, Joerg
2011-04-18 15:53       ` H. Peter Anvin
2011-04-18 14:54     ` H. Peter Anvin
2011-04-18 14:59       ` Roedel, Joerg
2011-04-18 15:50         ` Ingo Molnar
2011-04-19  6:12           ` Roedel, Joerg
2011-04-19  7:25             ` Ingo Molnar
2011-04-19  9:15               ` [PATCH] x86, gart: Rename pci-gart_64.c to amd64_gart.c Roedel, Joerg
2011-04-19 13:43               ` [PATCH 4/4] x86, gart: Make sure GART does not map physmem above 1TB H. Peter Anvin
2011-04-19 14:29                 ` Roedel, Joerg
2011-04-20 17:38                   ` H. Peter Anvin [this message]
2011-05-10 15:32                     ` [PATCH] x86, gart: Rename pci-gart_64.c to amd_gart_64.c 1TB Roedel, Joerg
2011-04-18 16:40   ` [tip:x86/urgent] x86, gart: Make sure GART does not map physmem above 1TB tip-bot for Joerg Roedel

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=4DAF1A14.2090703@kernel.org \
    --to=hpa@kernel.org \
    --cc=Joerg.Roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox