From: Sarah Newman <srn@prgmr.com>
To: Jan Beulich <JBeulich@suse.com>,
George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Yanhai Zhu <zhu.yanhai@gmail.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH] x86: Control CR0 TS behavior using dev_na_ts_allowed
Date: Tue, 18 Mar 2014 10:48:45 -0700 [thread overview]
Message-ID: <532886FD.6000100@prgmr.com> (raw)
In-Reply-To: <5327082D0200007800124BD0@nat28.tlf.novell.com>
On 03/17/2014 06:35 AM, Jan Beulich wrote:
>>>> On 17.03.14 at 13:44, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
>> On Mon, Mar 17, 2014 at 8:38 AM, Jan Beulich <JBeulich@suse.com> 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.
OK, I'll make a name change from dev_na_ts_allowed to nm_hardware_ts.
next prev parent reply other threads:[~2014-03-18 17:48 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 16:17 [PATCHv1] x86: don't schedule when handling #NM exception David Vrabel
2014-03-10 16:40 ` H. Peter Anvin
2014-03-10 16:40 ` H. Peter Anvin
2014-03-10 17:15 ` David Vrabel
2014-03-10 17:25 ` H. Peter Anvin
2014-03-10 17:25 ` H. Peter Anvin
2014-03-17 3:13 ` Sarah Newman
2014-03-17 3:13 ` Sarah Newman
2014-03-17 3:30 ` [PATCH] x86: Control CR0 TS behavior using dev_na_ts_allowed Sarah Newman
2014-03-17 8:38 ` Jan Beulich
2014-03-17 12:42 ` George Dunlap
2014-03-17 13:35 ` Jan Beulich
2014-03-17 14:05 ` George Dunlap
2014-03-17 14:18 ` George Dunlap
2014-03-17 15:28 ` Jan Beulich
2014-03-18 18:07 ` Sarah Newman
2014-03-18 19:14 ` David Vrabel
2014-03-17 12:44 ` George Dunlap
2014-03-17 13:35 ` Jan Beulich
2014-03-18 17:48 ` Sarah Newman [this message]
2014-03-17 3:32 ` [PATCH] x86, fpu, xen: Allocate fpu state for xen pv based on PVABI behavior Sarah Newman
2014-03-17 3:32 ` Sarah Newman
2014-03-17 3:33 ` [PATCHv1] x86: don't schedule when handling #NM exception H. Peter Anvin
2014-03-17 3:35 ` Sarah Newman
2014-03-17 3:35 ` [Xen-devel] " Sarah Newman
2014-03-17 3:43 ` H. Peter Anvin
2014-03-17 4:12 ` Sarah Newman
2014-03-17 4:12 ` [Xen-devel] " Sarah Newman
2014-03-17 4:23 ` H. Peter Anvin
2014-03-20 0:00 ` Greg Kroah-Hartman
2014-03-20 0:00 ` [Xen-devel] " Greg Kroah-Hartman
2014-03-20 2:29 ` H. Peter Anvin
2014-03-20 2:29 ` H. Peter Anvin
2014-03-17 4:23 ` H. Peter Anvin
2014-03-17 13:29 ` [Xen-devel] " David Vrabel
2014-03-19 13:21 ` Konrad Rzeszutek Wilk
2014-03-19 15:02 ` H. Peter Anvin
2014-03-19 15:02 ` [Xen-devel] " H. Peter Anvin
2014-06-23 13:08 ` Konrad Rzeszutek Wilk
2015-03-05 22:08 ` H. Peter Anvin
2015-03-05 22:08 ` [Xen-devel] " H. Peter Anvin
2015-03-06 11:46 ` [PATCHv4] x86, fpu: remove the logic of non-eager fpu mem allocation at the first usage David Vrabel
2015-03-06 11:46 ` David Vrabel
2014-06-23 13:08 ` [PATCHv1] x86: don't schedule when handling #NM exception Konrad Rzeszutek Wilk
2014-03-19 13:21 ` Konrad Rzeszutek Wilk
2014-03-17 13:29 ` David Vrabel
2014-03-17 3:43 ` H. Peter Anvin
2014-03-17 12:19 ` George Dunlap
2014-03-17 12:19 ` [Xen-devel] " George Dunlap
2014-03-17 16:55 ` H. Peter Anvin
2014-03-17 16:55 ` [Xen-devel] " H. Peter Anvin
2014-03-17 17:05 ` Jan Beulich
2014-03-17 17:05 ` [Xen-devel] " Jan Beulich
2014-03-17 17:12 ` H. Peter Anvin
2014-03-18 8:14 ` Ingo Molnar
2014-03-18 8:14 ` Ingo Molnar
2014-03-17 17:12 ` H. Peter Anvin
2014-03-17 17:14 ` [Xen-devel] " George Dunlap
2014-03-18 18:17 ` Sarah Newman
2014-03-18 18:27 ` H. Peter Anvin
2014-03-18 18:27 ` H. Peter Anvin
2014-03-18 18:17 ` Sarah Newman
2014-03-17 17:14 ` George Dunlap
2014-03-17 3:33 ` H. Peter Anvin
2014-03-10 17:15 ` David Vrabel
2014-03-10 16:45 ` H. Peter Anvin
2014-03-10 16:45 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=532886FD.6000100@prgmr.com \
--to=srn@prgmr.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xenproject.org \
--cc=zhu.yanhai@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.