On Tue, 2018-01-09 at 09:15 -0200, Murilo Opsfelder Araújo wrote: > On 01/09/2018 07:21 AM, Suraj Jitindar Singh wrote: > > This patch adds three new capabilities: > > cap-cfpc -> safe_cache > > cap-sbbc -> safe_bounds_check > > cap-ibs -> safe_indirect_branch > > Hi, Suraj. > > What about splitting this into smaller patches, one per capability?
Yep > > > Each capability is tristate with the possible values "broken", > > "workaround" or "fixed". Add generic getter and setter functions > > for > > this new capability type. Add these new capabilities to the > > capabilities > > list. The maximum value for the capabilities is queried from kvm > > through > > new kvm capabilities. The requested values are considered to be > > compatible if kvm can support an equal or higher value for each > > capability. > > > > Discussion: > > Currently these new capabilities default to broken to allow for > > backwards compatibility, is this the best option? > > This could be placed in the cover letter, not in the commit Only here because this is an RFC > > Cheers > Murilo >
