From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sergey Dyasli <sergey.dyasli@citrix.com>, xen-devel@lists.xen.org
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v1] x86/msr: add Raw and Host domain policies
Date: Thu, 8 Feb 2018 11:08:46 +0000 [thread overview]
Message-ID: <be5ba061-d6ce-1add-fc45-3d5fd46ac078@citrix.com> (raw)
In-Reply-To: <20180208102321.25193-1-sergey.dyasli@citrix.com>
On 08/02/18 10:23, Sergey Dyasli wrote:
> Raw policy contains the actual values from H/W MSRs. Add PLATFORM_INFO
> msr to the policy during probe_cpuid_faulting().
>
> Host policy might have certain features disabled if Xen decides not
> to use them. For now, make Host policy equal to Raw policy.
>
> Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
Ah thanks - I was about to ask you whether you had this patch to hand.
The deferral probe_cpuid_faulting() isn't great but I think is necessary
at the moment. I've got some plans to reorder early startup somewhat,
but more infrastructure is required before that can work.
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-08 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 10:23 [PATCH v1] x86/msr: add Raw and Host domain policies Sergey Dyasli
2018-02-08 11:08 ` Andrew Cooper [this message]
2018-02-08 11:21 ` Roger Pau Monné
2018-02-08 11:29 ` Sergey Dyasli
2018-02-15 13:33 ` Jan Beulich
2018-02-16 10:33 ` Sergey Dyasli
2018-02-16 11:06 ` Jan Beulich
2018-02-16 11:31 ` Sergey Dyasli
2018-02-16 11:37 ` Jan Beulich
2018-02-16 11:38 ` Andrew Cooper
2018-02-16 16:00 ` Sergey Dyasli
2018-02-16 16:02 ` Andrew Cooper
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=be5ba061-d6ce-1add-fc45-3d5fd46ac078@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=sergey.dyasli@citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).