RFR: 8079315: UseCondCardMark broken in conjunction with CMS precleaning
vitalyd at gmail.com
Wed May 6 12:41:13 UTC 2015
Mikael's suggestion was to make mutator check for !clean and then mark
dirty. If it sees stale dirty, it will write dirty again no? Today's code
would have this problem because it's checking for !dirty, but I thought the
suggested change would prevent that.
sent from my phone
On May 6, 2015 4:53 AM, "Andrew Haley" <aph at redhat.com> wrote:
> On 05/05/15 20:51, Vitaly Davidovich wrote:
> > If mutator doesn't see "clean" due to staleness, won't it just mark it
> > dirty "unnecessarily" using Mikael's suggestion?
> No. The mutator may see a stale "dirty" and not write anything. At least
> I haven't seen anything which certainly will prevent that from happening.
More information about the hotspot-dev