Re: [patch 0/4] [RFC] MMU Notifiers V1
- From: Christoph Lameter <clameter@xxxxxxx>
- Date: Fri, 25 Jan 2008 13:25:50 -0800 (PST)
On Sat, 26 Jan 2008, Benjamin Herrenschmidt wrote:
Also, wouldn't there be a problem with something trying to use that
interface to keep in sync a secondary device MMU such as the DRM or
other accelerators, which might need virtual address based
invalidation ?
Yes just doing the rmap based solution would have required DRM etc to
maintain their own rmaps. So it looks that we need to go with both
variants. Note that secondary device MMUs that need to run code outside of
atomic context may still need to create their own rmaps.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [patch 0/4] [RFC] MMU Notifiers V1
- From: Christoph Lameter
- Re: [patch 0/4] [RFC] MMU Notifiers V1
- From: Andrea Arcangeli
- Re: [patch 0/4] [RFC] MMU Notifiers V1
- From: Benjamin Herrenschmidt
- [patch 0/4] [RFC] MMU Notifiers V1
- Prev by Date: [PATCH 4/8] X86: export information about NPT to generic x86 code
- Next by Date: Re: [kvm-devel] [PATCH][RFC] SVM: Add Support for Nested Paging in AMD Fam16 CPUs
- Previous by thread: Re: [patch 0/4] [RFC] MMU Notifiers V1
- Next by thread: Re: [patch 0/4] [RFC] MMU Notifiers V1
- Index(es):