search for: _writable

...put in the "root" of a subvolume: think about >> compress/nocompress, (no)datasum...) >> - For the reason abowe, I suggest to replace SNAPSHOT with SUBVOLUME >> - Finally, with a pair of get/set_flags functions we can avoid the use of the >> flags BTRFS_SNAPSHOT_WRITABLE. >> > >There are some reasons that I created this interface: > >- set/getflags should set/get root flags which reflect in struct >btrfs_root_item->flags. > >- btrfs_root_item->flags was not used at all before this patch, so >(no)compress and (no)datasum is not r...

...lback to the - guest if the above segment fixups are used: allows the guest to +\item[VMASST\_TYPE\_4gb\_segments\_notify] Provide a callback (via trap number + 15) to the guest if the above segment fixups are used: allows the guest to display a warning message during boot. \item[VMASST\_TYPE\_writable\_pagetables] Enable writable pagetable mode - described above. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...with per-page dirty bits a small optimization. Whenever a writable pte is created a check is added that allows to move the page into the correct state. This needs to be done before the writable pte is established. To avoid unnecessary state transitions and the need for a counter, a new page flag PG_writable is added. Only the creation of the first writable pte will do a page state change. Even if all the writable ptes pointing to a page are removed again, the page stays in the safe state until all read-only users of the page have unmapped it as well. Only then is the PG_writable bit reset. The state...

...with per-page dirty bits a small optimization. Whenever a writable pte is created a check is added that allows to move the page into the correct state. This needs to be done before the writable pte is established. To avoid unnecessary state transitions and the need for a counter, a new page flag PG_writable is added. Only the creation of the first writable pte will do a page state change. Even if all the writable ptes pointing to a page are removed again, the page stays in the safe state until all read-only users of the page have unmapped it as well. Only then is the PG_writable bit reset. The state...

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.

Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.

After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic

After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic