>-Original Message-
>From: Dave Jones [mailto:[EMAIL PROTECTED]
>Sent: Friday, January 18, 2008 7:29 PM
>To: Ingo Molnar
>Cc: Yinghai Lu; Pallipadi, Venkatesh; LKML
>Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT
>
>On Fri, Jan 18, 2008 at 10:02:10PM
-Original Message-
From: Dave Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, January 18, 2008 7:29 PM
To: Ingo Molnar
Cc: Yinghai Lu; Pallipadi, Venkatesh; LKML
Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT
On Fri, Jan 18, 2008 at 10:02:10PM +0100, Ingo Molnar wrote:
* Dave
On Friday 18 January 2008 07:28:49 pm Dave Jones wrote:
> On Fri, Jan 18, 2008 at 10:02:10PM +0100, Ingo Molnar wrote:
> >
> > * Dave Jones <[EMAIL PROTECTED]> wrote:
> >
> > > > you mean modifies MTRRs? Which code is that? (besides the
> > > > /proc/mtrr userspace API)
> > >
> > >
On Fri, Jan 18, 2008 at 10:02:10PM +0100, Ingo Molnar wrote:
>
> * Dave Jones <[EMAIL PROTECTED]> wrote:
>
> > > you mean modifies MTRRs? Which code is that? (besides the
> > > /proc/mtrr userspace API)
> >
> > This exclusion is going to be a real pain in the ass for distro
> >
* Pallipadi, Venkatesh <[EMAIL PROTECTED]> wrote:
> Ingo, can you remove this PAT MTRR exclusion.
yeah, already did that.
> Actually, this exclusion will not work at all with the current code.
> Infact it should be PAT selects MTRR, for the current code. As
> pat_init() is called during mtrr
* Dave Jones <[EMAIL PROTECTED]> wrote:
> > you mean modifies MTRRs? Which code is that? (besides the
> > /proc/mtrr userspace API)
>
> This exclusion is going to be a real pain in the ass for distro
> kernels. It's impossible for example to build a kernel that will now
> support the
On Fri, Jan 18, 2008 at 10:47:05AM -0800, Venki Pallipadi wrote:
> >This exclusion is going to be a real pain in the ass for
> >distro kernels.
> >It's impossible for example to build a kernel that will now support
> >the MTRR-alike registers on the AMD K6/early Cyrix etc and also
>
>-Original Message-
>From: Dave Jones [mailto:[EMAIL PROTECTED]
>Sent: Friday, January 18, 2008 10:25 AM
>To: Ingo Molnar
>Cc: Yinghai Lu; Pallipadi, Venkatesh; LKML
>Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT
>
>On Fri, Jan 18, 2008 at 01:31:40PM
On Fri, Jan 18, 2008 at 01:31:40PM +0100, Ingo Molnar wrote:
> * Yinghai Lu <[EMAIL PROTECTED]> wrote:
>
> > > thanks. But, i think we should rather do the following: if X86_PAT
> > > is eanbled then /proc/mtrr should be read-only. There's no problem
> > > _looking_ at MTRR contents, as
* Yinghai Lu <[EMAIL PROTECTED]> wrote:
> > thanks. But, i think we should rather do the following: if X86_PAT
> > is eanbled then /proc/mtrr should be read-only. There's no problem
> > _looking_ at MTRR contents, as long as we do not try to modify them.
> > Hm?
>
> anyway
>
> depends on
On Friday 18 January 2008 12:10:40 am Ingo Molnar wrote:
>
> * Yinghai Lu <[EMAIL PROTECTED]> wrote:
>
> > config MTRR
> > bool "MTRR (Memory Type Range Register) support"
> > - depends on !PAT
> > + depends on !X86_PAT
> > ---help---
> > On Intel P6 family processors (Pentium
* Yinghai Lu <[EMAIL PROTECTED]> wrote:
> config MTRR
> bool "MTRR (Memory Type Range Register) support"
> - depends on !PAT
> + depends on !X86_PAT
> ---help---
> On Intel P6 family processors (Pentium Pro, Pentium II and later)
> the Memory Type Range
On Friday 18 January 2008 12:10:40 am Ingo Molnar wrote:
* Yinghai Lu [EMAIL PROTECTED] wrote:
config MTRR
bool MTRR (Memory Type Range Register) support
- depends on !PAT
+ depends on !X86_PAT
---help---
On Intel P6 family processors (Pentium Pro, Pentium II
* Pallipadi, Venkatesh [EMAIL PROTECTED] wrote:
Ingo, can you remove this PAT MTRR exclusion.
yeah, already did that.
Actually, this exclusion will not work at all with the current code.
Infact it should be PAT selects MTRR, for the current code. As
pat_init() is called during mtrr init
* Dave Jones [EMAIL PROTECTED] wrote:
you mean modifies MTRRs? Which code is that? (besides the
/proc/mtrr userspace API)
This exclusion is going to be a real pain in the ass for distro
kernels. It's impossible for example to build a kernel that will now
support the MTRR-alike
On Fri, Jan 18, 2008 at 01:31:40PM +0100, Ingo Molnar wrote:
* Yinghai Lu [EMAIL PROTECTED] wrote:
thanks. But, i think we should rather do the following: if X86_PAT
is eanbled then /proc/mtrr should be read-only. There's no problem
_looking_ at MTRR contents, as long as we do
On Fri, Jan 18, 2008 at 10:47:05AM -0800, Venki Pallipadi wrote:
This exclusion is going to be a real pain in the ass for
distro kernels.
It's impossible for example to build a kernel that will now support
the MTRR-alike registers on the AMD K6/early Cyrix etc and also
support PAT.
On Fri, Jan 18, 2008 at 10:02:10PM +0100, Ingo Molnar wrote:
* Dave Jones [EMAIL PROTECTED] wrote:
you mean modifies MTRRs? Which code is that? (besides the
/proc/mtrr userspace API)
This exclusion is going to be a real pain in the ass for distro
kernels. It's
* Yinghai Lu [EMAIL PROTECTED] wrote:
thanks. But, i think we should rather do the following: if X86_PAT
is eanbled then /proc/mtrr should be read-only. There's no problem
_looking_ at MTRR contents, as long as we do not try to modify them.
Hm?
anyway
depends on !PAT
need to
-Original Message-
From: Dave Jones [mailto:[EMAIL PROTECTED]
Sent: Friday, January 18, 2008 10:25 AM
To: Ingo Molnar
Cc: Yinghai Lu; Pallipadi, Venkatesh; LKML
Subject: Re: [PATCH] X86: fix typo PAT to X86_PAT
On Fri, Jan 18, 2008 at 01:31:40PM +0100, Ingo Molnar wrote:
* Yinghai
On Friday 18 January 2008 07:28:49 pm Dave Jones wrote:
On Fri, Jan 18, 2008 at 10:02:10PM +0100, Ingo Molnar wrote:
* Dave Jones [EMAIL PROTECTED] wrote:
you mean modifies MTRRs? Which code is that? (besides the
/proc/mtrr userspace API)
This exclusion is going
21 matches
Mail list logo
