https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234733
--- Comment #20 from sig...@gmail.com --- Maybe it could do some double checking only once to "learn" about those registers' behavior (and maybe have a sysctl to reset that to make it check again)? But if Linux ignores it entirely then you'd think it's probably safe to do that everywhere in practice. Maybe a sysctl/tunable to enable/disable the check just in case? On this one maybe that's not even an "implemented" register (if that makes sense), it just follows the other one and can't really be set independently (and it "follows" it wrong according to the specs it seems). Really not sure I understand most of this though. If Linux (and maybe Windows too) ignores it maybe the register is nonsense on other machines too and it goes unnoticed. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
