- User Since
- May 16 2014, 7:35 PM (417 w, 2 d)
Sat, May 14
You just merge it when you think that there is enough testing done in head, as usual. Or, is there some more background context I am not aware of?
Fri, May 13
Mon, May 9
I checked for the described condition by testing for rv == 1. Then it does not need this long comment.
Sun, May 8
Sat, May 7
Space in .Dv NULL ,
Bump man page date in advance.
Fri, May 6
Thu, May 5
Wed, May 4
Mon, May 2
Thu, Apr 28
Wed, Apr 27
Does it make sense to add asserts in the demotion code to ensure that it does not touch pcpu mappings? Or even, somewhat more to the point, in the break-before-make code.
Avoid LOR between stop_all_proc_block() and proctree_lock.
Tue, Apr 26
I do not quite understand this. Am I right that the intent is to see zombies under linprocfs? If yes, what exact entries from the pid directory should be exposed?
Use sx for stop_all_proc_block().
Upgrade proctree_lock assert to XLOCKED in reaper_abandon_children().
Fix condition for need_stop: it should check that REAPER_KILL_CHILDREN is not set. REAPER_KILL_SUBTREE is legitimately unset when all descendants of the reaper must be killed.
Mon, Apr 25
Handle Mark' comments.
Fix error/errno meh.
Sun, Apr 24
Sat, Apr 23
Stop the victim while signalling.
Thu, Apr 21
Wed, Apr 20
Per-commit view is available at https://kib.kiev.ua/git/gitweb.cgi?p=deviant3.git;a=shortlog;h=refs/heads/reap
If this is a laptop (judging by ahci/amount of memory), you most likely have two DMARs, one serving the GPU, and another covering all PCIe devices. In this configuration, whatever was protected by PMR for GPU, does not make sense to unprotect.
Tue, Apr 19
As a second though, this control is global. Do you want it to be per-DMAR unit, in fact? [I am fine with this refine to be done later]
Doesnt' all real-time priority threads run to completion? In other words, if all ithreads are put under the same priority, then there is no preemption to let other ithread to run until current ithread finishes? To put it differently, making ithreads time-share interrupt time requires changes to the schedulers, not just adjusting the priorities.
BTW, should PAGE_SIZE be the least guaranteed page size? In other words, should some test ensure _Static_assert(PAGE_SIZE <= ps). Also perhaps something about ps being multiple of PAGE_SIZE worth to be guaranteed?
Sat, Apr 16
Regardless of the notes I put above, please mail me the git patch with the correct 'Author' metadata.
I am not sure that I like/agree with the patch. My main objection is that you are unconditionally tickle PMR despite DMAR state. In fact, it is quite far from the place where you put the call to dmar_disable_protected_regions(), to the actual enable of translation.