All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Sarah Newman <srn@prgmr.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Yanhai Zhu <zhu.yanhai@gmail.com>
Subject: Re: [PATCH] x86: Control CR0 TS behavior using	dev_na_ts_allowed
Date: Tue, 18 Mar 2014 19:14:22 +0000	[thread overview]
Message-ID: <53289B0E.9070900@citrix.com> (raw)
In-Reply-To: <53288B71.8030703@prgmr.com>

On 18/03/14 18:07, Sarah Newman wrote:
> 
> The guest cannot enable or disable this behavior but it can detect the behavior using CPUID.  I
> considered making the behavior configurable from within the guest, but did not find a clean way of
> implementing it since any decision should really happen very early in the boot process.  Suggestions
> on how to do this are welcome.

Consider using an Xen ELF note feature (see public/elfnote.h and
public/features.h).

e.g., XENFEAT_nm_hardware_ts

This would be a trivial one-liner to the kernel and would require no
user configurable option in the toolstack and compatibility would be
retained for guests needing the current ABI.

David

  reply	other threads:[~2014-03-18 19:14 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: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 [this message]
2014-03-17 12:44           ` George Dunlap
2014-03-17 13:35             ` Jan Beulich
2014-03-18 17:48               ` Sarah Newman
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:23               ` H. Peter Anvin
2014-03-17  4:23               ` [Xen-devel] " 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                   ` [Xen-devel] " H. Peter Anvin
2014-03-17  4:12             ` Sarah Newman
2014-03-17 13:29             ` [Xen-devel] " David Vrabel
2014-03-19 13:21               ` Konrad Rzeszutek Wilk
2014-03-19 13:21               ` [Xen-devel] " 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
2014-06-23 13:08                   ` [Xen-devel] " 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-03-17 13:29             ` [PATCHv1] x86: don't schedule when handling #NM exception 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:12               ` H. Peter Anvin
2014-03-17 17:12               ` [Xen-devel] " H. Peter Anvin
2014-03-18  8:14                 ` Ingo Molnar
2014-03-18  8:14                 ` [Xen-devel] " Ingo Molnar
2014-03-17 17:14               ` George Dunlap
2014-03-18 18:17                 ` Sarah Newman
2014-03-18 18:17                 ` [Xen-devel] " Sarah Newman
2014-03-18 18:27                   ` H. Peter Anvin
2014-03-18 18:27                     ` H. Peter Anvin
2014-03-17 17:14               ` George Dunlap
2014-03-17 17:05             ` Jan Beulich
2014-03-17  3:33       ` H. Peter Anvin
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=53289B0E.9070900@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=srn@prgmr.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.