[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86: Control CR0 TS behavior using dev_na_ts_allowed



>>> On 17.03.14 at 13:44, George Dunlap <George.Dunlap@xxxxxxxxxxxxx> wrote:
> On Mon, Mar 17, 2014 at 8:38 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>> The naming of this (here and elsewhere) is rather odd: I assume
>> you mean "dev_na" to be an abbreviation of "device not available",
>> but I'd much prefer the CPU exception abbreviation (#NM) to be
>> used in such a case. However, in the case here this still wouldn't
>> be a precise description of the behavior you establish: TS being
>> set isn't allowed, but required to be set upon guest #NM. I'd
>> therefore suggest naming this along the lines of "nm_enforce_ts".
> 
> nm_hardware_ts, perhaps, since the TS is mimicking the native hardware
> interface?

Would be fine with me too.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.