Re: [PATCH] trim memory not covered by WB MTRRs

On Wednesday, June 27, 2007 9:00:33 Pim Zandbergen wrote:
> Jesse Barnes wrote:
> > Yeah, you're right I should use an unsigned format string.  Pim, if
> > you change it to %lu does the printk in your dmesg look better?
>
> Er, no.
>
> **** MTRRs don't cover all of memory, trimmed 18446744073709486080
> pages

It looks like end_pfn might be ~0UL now... can you print that out in 
your configuration?

Thanks,
Jesse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] trim memory not covered by WB MTRRs
  - From: Pim Zandbergen <[email protected]>

References:
- [PATCH] trim memory not covered by WB MTRRs
  - From: Jesse Barnes <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
  - From: Jesse Barnes <[email protected]>
- Re: [PATCH] trim memory not covered by WB MTRRs
  - From: Pim Zandbergen <[email protected]>

Prev by Date: Re: [md-accel PATCH 03/19] xor: make 'xor_blocks' a library routine for use with async_tx
Next by Date: Re: Is it time for remove (crap) ALSA from kernel tree ?
Previous by thread: Re: [PATCH] trim memory not covered by WB MTRRs
Next by thread: Re: [PATCH] trim memory not covered by WB MTRRs
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]