- User Since
- May 16 2014, 7:35 PM (319 w, 6 d)
It is fine, except one detail that I do not like. You do the late pass after the APs were released.
Provide the amd64 example, in binary form.
bhyve: Handle guest' LA57 paging mode.
This is in fact independent of the rest of the patch, since guest can set the bit in %cr4 at will.
Refresh patch after rebase. Fix conflicts in vm_map.c.
Wed, Jul 1
vn_io_fault() is not used for shmfd.
Tue, Jun 30
I realized that we do not check for the overflow in vn_io_fault() either.
I am fine with this commit as-is, and you could fix vn_io_fault() (if needed) later.
For instance, despite no check on filedesc/VFS layer, ffs_write() eventually does
if ((uoff_t)uio->uio_offset + uio->uio_resid > fs->fs_maxfilesize) return (EFBIG);
which probably is good enough to avoid corruption for FFS.
But rangelocks are probably not immune.
Mon, Jun 29
Fix pv list locking in pmap_remove_pde(), restore assert in pmap_delayed_invl_page().
Sun, Jun 28
Handle the latest batch of reviewer' notes.
My intent was to try to split commits. Maintaining the split with git-svn workflow is too much work.
Add asserts about interrupt enable state.
Collape pmap_activate_sw_pcid_pti1() into the caller.
Sat, Jun 27
Update description of ptepindex.
I think this is fine on principle.
In which way ?
Where is VHOLD_NO_SMR set ?
Fri, Jun 26
Separately mention the root page.
Change herald sentence as suggested by Mark. Add articles.
Thu, Jun 25
We did not, because the dso version was bumped.
Handle the first round of comments.
Wed, Jun 24
Tue, Jun 23
I am not sure what you see in dtrace, but I see a bug in ffs_write() regardless of IO_DATASYNC. D25404