From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCHv1 5/5] x86/domctl: Add XEN_DOMCTL_PARAM_ARCH_X86_FIP_WIDTH parameter
Date: Fri, 19 Feb 2016 10:05:31 +0000 [thread overview]
Message-ID: <56C6E8EB.8030605@citrix.com> (raw)
In-Reply-To: <1455821530-4263-6-git-send-email-david.vrabel@citrix.com>
On 18/02/16 18:52, David Vrabel wrote:
> Add a parameter to allow the toolstack to set the x87 FIP width in case
> the hypervisor's heuristics do the wrong thing.
I think this would be better as a HVM param since: a) it only needs to
be changed for HVM guests; b) it would allow the guest agent or OS
(which may be able to make a better decision) to set it; and c) it can
be saved/restored across a migrate.
David
>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> ---
> xen/arch/x86/domctl.c | 10 ++++++++++
> xen/include/public/domctl.h | 1 +
> 2 files changed, 11 insertions(+)
>
> diff --git a/xen/arch/x86/domctl.c b/xen/arch/x86/domctl.c
> index 3a3ebbf..f75cd69 100644
> --- a/xen/arch/x86/domctl.c
> +++ b/xen/arch/x86/domctl.c
> @@ -1415,6 +1415,16 @@ int arch_domctl_param(struct domain *d, uint32_t param, bool_t set,
>
> switch ( param )
> {
> + case XEN_DOMCTL_PARAM_ARCH_X86_FIP_WIDTH:
> + *value = d->arch.x87_fip_width;
> + if ( set )
> + {
> + if ( new_value != 0 && new_value != 4 && new_value != 8 )
> + return -EINVAL;
> + d->arch.x87_fip_width = new_value;
> + }
> + break;
> +
> default:
> return -EINVAL;
> }
> diff --git a/xen/include/public/domctl.h b/xen/include/public/domctl.h
> index 330b3e7..26d4096 100644
> --- a/xen/include/public/domctl.h
> +++ b/xen/include/public/domctl.h
> @@ -1100,6 +1100,7 @@ DEFINE_XEN_GUEST_HANDLE(xen_domctl_psr_cat_op_t);
> *
> * Not all parameters are valid for all architectures or domain types.
> */
> +#define XEN_DOMCTL_PARAM_ARCH_X86_FIP_WIDTH 0
> #define XEN_DOMCTL_PARAM_SET (1u << 31)
>
> struct xen_domctl_param {
>
next prev parent reply other threads:[~2016-02-19 10:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:52 [RFC PATCH 0/5] x86: workaround inability to fully restore FPU state David Vrabel
2016-02-18 18:52 ` [PATCHv1 1/5] domctl: Add op to get/set generic numeric parameters David Vrabel
2016-02-18 19:02 ` Andrew Cooper
2016-02-19 13:59 ` Jan Beulich
2016-02-18 18:52 ` [PATCHv1 2/5] tools/libxc: add xc_domain_get_param() and xc_domain_set_param() David Vrabel
2016-02-18 19:03 ` Andrew Cooper
2016-02-18 18:52 ` [PATCHv1 3/5] x86/fpu: Add a per-domain field to set the width of FIP/FDP David Vrabel
2016-02-18 19:13 ` Andrew Cooper
2016-02-19 10:03 ` David Vrabel
2016-02-19 14:08 ` Jan Beulich
2016-02-19 14:16 ` David Vrabel
2016-02-19 14:36 ` Jan Beulich
2016-02-19 14:49 ` David Vrabel
2016-02-19 15:14 ` Jan Beulich
2016-02-19 15:43 ` David Vrabel
2016-02-19 16:38 ` David Vrabel
2016-02-19 17:20 ` Jan Beulich
2016-02-18 18:52 ` [PATCHv1 4/5] x86/viridian: set x87 FIP width to 4 for Windows guests David Vrabel
2016-02-18 19:19 ` Andrew Cooper
2016-02-19 14:11 ` Jan Beulich
2016-02-18 18:52 ` [PATCHv1 5/5] x86/domctl: Add XEN_DOMCTL_PARAM_ARCH_X86_FIP_WIDTH parameter David Vrabel
2016-02-19 10:05 ` David Vrabel [this message]
2016-02-19 14:13 ` Jan Beulich
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=56C6E8EB.8030605@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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.