Prev: [PATCH 1/4] input: Introduce buflock, a one-to-many circular buffer mechanism
Next: scripts: add nconf into gitignore file
From: Nigel Cunningham on 3 Jun 2010 04:20 Hi. On 30/05/10 15:25, Pavel Machek wrote: > Hi! > >> 2. Prior to writing any of the image, also set up new 4k page tables >> such that an attempt to make a change to any of the pages we're about to >> write to disk will result in a page fault, giving us an opportunity to >> flag the page as needing an atomic copy later. Once this is done, write >> protection for the page can be disabled and the write that caused the >> fault allowed to proceed. > > Tricky. > > page faulting code touches memory, too... Yeah. I realise we'd need to make the pages that are used to record the faults be unprotected themselves. I'm imagining a bitmap for that. Do you see any reason that it could be inherently impossible? That's what I really want to know before (potentially) wasting time trying it. Regards, Nigel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pavel Machek on 3 Jun 2010 04:20
Hi! > 2. Prior to writing any of the image, also set up new 4k page tables > such that an attempt to make a change to any of the pages we're about to > write to disk will result in a page fault, giving us an opportunity to > flag the page as needing an atomic copy later. Once this is done, write > protection for the page can be disabled and the write that caused the > fault allowed to proceed. Tricky. page faulting code touches memory, too... -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |