Re: update_mmu_cache(): fault or not fault ?

> So I suggest adding an argument to it "int is_fault", that would
> basically be '1' on all the call sites in mm/memory.c and '0' in all the
> call sites in mm/fremap.c.
> 
> Any objection, comment, whatever, before I come up with a patch adding
> it to all archs ?

Acutally, that wouldn't work for calls to get_user_pages() which will
cause the fault code path on non-faults... looks like David's solution
is the best one at this point.

Ben.


-
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/

---

• References:
  • update_mmu_cache(): fault or not fault ?
    • From: Benjamin Herrenschmidt <[email protected]>

• Prev by Date: Re: update_mmu_cache(): fault or not fault ?
• Next by Date: Re: How to add a new ram region ?
• Previous by thread: Re: update_mmu_cache(): fault or not fault ?
• Next by thread: [PATCH] missing dependency on arm O= builds
• Index(es):
  • Date
  • Thread

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