H. Peter Anvin wrote:
William Lee Irwin III wrote:
Robert P. J. Day wrote:
although it's not clear where in the source tree are the invocations
that would actually make a difference to a MIPS system, which is why
i've CC'ed ralf on this. i'm sure he can clear this up. :-)
On Thu, Jun 07,
H. Peter Anvin wrote:
William Lee Irwin III wrote:
Robert P. J. Day wrote:
although it's not clear where in the source tree are the invocations
that would actually make a difference to a MIPS system, which is why
i've CC'ed ralf on this. i'm sure he can clear this up. :-)
On Thu, Jun 07,
Robert P. J. Day wrote:
>
> and once again, an initially innocuous question quickly leaves me
> behind. no, no, i'm getting used to it. :-P
>
This is what happens when you stir the muck on the bottom. This is
probably a good thing.
-hpa
-
To unsubscribe from this list: send the line
On Thu, 7 Jun 2007, H. Peter Anvin wrote:
> William Lee Irwin III wrote:
> > Robert P. J. Day wrote:
> >>> although it's not clear where in the source tree are the invocations
> >>> that would actually make a difference to a MIPS system, which is why
> >>> i've CC'ed ralf on this. i'm sure he
On Thu, 7 Jun 2007, H. Peter Anvin wrote:
William Lee Irwin III wrote:
Robert P. J. Day wrote:
although it's not clear where in the source tree are the invocations
that would actually make a difference to a MIPS system, which is why
i've CC'ed ralf on this. i'm sure he can clear this
Robert P. J. Day wrote:
and once again, an initially innocuous question quickly leaves me
behind. no, no, i'm getting used to it. :-P
This is what happens when you stir the muck on the bottom. This is
probably a good thing.
-hpa
-
To unsubscribe from this list: send the line
William Lee Irwin III wrote:
> Robert P. J. Day wrote:
>>> although it's not clear where in the source tree are the invocations
>>> that would actually make a difference to a MIPS system, which is why
>>> i've CC'ed ralf on this. i'm sure he can clear this up. :-)
>
> On Thu, Jun 07, 2007 at
Robert P. J. Day wrote:
>> although it's not clear where in the source tree are the invocations
>> that would actually make a difference to a MIPS system, which is why
>> i've CC'ed ralf on this. i'm sure he can clear this up. :-)
On Thu, Jun 07, 2007 at 10:32:29AM -0700, H. Peter Anvin wrote:
>
Ralf Baechle wrote:
> Cache aliases. When the same page of physical memory is mapped twice to
> user space, let's say at address addr and addr + PAGE_SIZE this is normally
> harmless although wasteful on processors with virtually indexed caches as
> long as the page is mapped read-only such as in
On Thu, Jun 07, 2007 at 07:53:08AM -0400, Robert P. J. Day wrote:
> > > > MIPS?
> > >
> > > argh. that would be the *one* definition whose output got chopped
> > > because of line continuation, and it would be only one that actually
> > > uses the argument:
> > >
> > > #define ZERO_PAGE(vaddr) \
Robert P. J. Day wrote:
>> The comment above empty_zero_page and zero_page_mask
>> declarations at arch/mips/mm/init.c:508 sheds light on this ...
>
> well, it *sort of* does. at line 64 of that file:
>
> /*
> * We have up to 8 empty zeroed pages so we can map one of the right colour
> * when
On Thu, 7 Jun 2007, Satyam Sharma wrote:
> On 6/7/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > On Thu, 7 Jun 2007, Nick Piggin wrote:
> >
> > > Robert P. J. Day wrote:
> > > > probably making a fool of myself here, but what is the purpose of
> > > > that single argument to the macro
On 6/7/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
On Thu, 7 Jun 2007, Nick Piggin wrote:
> Robert P. J. Day wrote:
> > probably making a fool of myself here, but what is the purpose of
> > that single argument to the macro "ZERO_PAGE"?
> >
> > $ grep -r "define ZERO_PAGE" include
> >
On Thu, 7 Jun 2007, Nick Piggin wrote:
> Robert P. J. Day wrote:
> > probably making a fool of myself here, but what is the purpose of
> > that single argument to the macro "ZERO_PAGE"?
> >
> > $ grep -r "define ZERO_PAGE" include
> > include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({
Robert P. J. Day wrote:
probably making a fool of myself here, but what is the purpose of
that single argument to the macro "ZERO_PAGE"?
$ grep -r "define ZERO_PAGE" include
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({ BUG(); NULL; })
include/asm-frv/pgtable.h:#define
probably making a fool of myself here, but what is the purpose of
that single argument to the macro "ZERO_PAGE"?
$ grep -r "define ZERO_PAGE" include
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({ BUG(); NULL; })
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr)
probably making a fool of myself here, but what is the purpose of
that single argument to the macro ZERO_PAGE?
$ grep -r define ZERO_PAGE include
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({ BUG(); NULL; })
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr)
Robert P. J. Day wrote:
probably making a fool of myself here, but what is the purpose of
that single argument to the macro ZERO_PAGE?
$ grep -r define ZERO_PAGE include
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({ BUG(); NULL; })
include/asm-frv/pgtable.h:#define
On Thu, 7 Jun 2007, Nick Piggin wrote:
Robert P. J. Day wrote:
probably making a fool of myself here, but what is the purpose of
that single argument to the macro ZERO_PAGE?
$ grep -r define ZERO_PAGE include
include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr) ({ BUG(); NULL; })
On 6/7/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Thu, 7 Jun 2007, Nick Piggin wrote:
Robert P. J. Day wrote:
probably making a fool of myself here, but what is the purpose of
that single argument to the macro ZERO_PAGE?
$ grep -r define ZERO_PAGE include
On Thu, 7 Jun 2007, Satyam Sharma wrote:
On 6/7/07, Robert P. J. Day [EMAIL PROTECTED] wrote:
On Thu, 7 Jun 2007, Nick Piggin wrote:
Robert P. J. Day wrote:
probably making a fool of myself here, but what is the purpose of
that single argument to the macro ZERO_PAGE?
$
Robert P. J. Day wrote:
The comment above empty_zero_page and zero_page_mask
declarations at arch/mips/mm/init.c:508 sheds light on this ...
well, it *sort of* does. at line 64 of that file:
/*
* We have up to 8 empty zeroed pages so we can map one of the right colour
* when needed.
On Thu, Jun 07, 2007 at 07:53:08AM -0400, Robert P. J. Day wrote:
MIPS?
argh. that would be the *one* definition whose output got chopped
because of line continuation, and it would be only one that actually
uses the argument:
#define ZERO_PAGE(vaddr) \
Ralf Baechle wrote:
Cache aliases. When the same page of physical memory is mapped twice to
user space, let's say at address addr and addr + PAGE_SIZE this is normally
harmless although wasteful on processors with virtually indexed caches as
long as the page is mapped read-only such as in
Robert P. J. Day wrote:
although it's not clear where in the source tree are the invocations
that would actually make a difference to a MIPS system, which is why
i've CC'ed ralf on this. i'm sure he can clear this up. :-)
On Thu, Jun 07, 2007 at 10:32:29AM -0700, H. Peter Anvin wrote:
x86
William Lee Irwin III wrote:
Robert P. J. Day wrote:
although it's not clear where in the source tree are the invocations
that would actually make a difference to a MIPS system, which is why
i've CC'ed ralf on this. i'm sure he can clear this up. :-)
On Thu, Jun 07, 2007 at 10:32:29AM
26 matches
Mail list logo
