All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/2] x86: report if PCID and INVPCID are supported
Date: Mon, 5 Mar 2018 13:26:46 +0000	[thread overview]
Message-ID: <20180305132646.762q3l55322xvi4g@citrix.com> (raw)
In-Reply-To: <5A9D4CDC02000078001AE820@prv-mh.provo.novell.com>

On Mon, Mar 05, 2018 at 05:57:48AM -0700, Jan Beulich wrote:
> >>> On 05.03.18 at 13:49, <jgross@suse.com> wrote:
> > On 05/03/18 13:37, Jan Beulich wrote:
> >>>>> On 05.03.18 at 12:43, <jgross@suse.com> wrote:
> >>> On 05/03/18 12:20, Jan Beulich wrote:
> >>>>>>> On 05.03.18 at 10:50, <wei.liu2@citrix.com> wrote:
> >>>>> --- a/xen/arch/x86/setup.c
> >>>>> +++ b/xen/arch/x86/setup.c
> >>>>> @@ -1701,6 +1701,13 @@ void __init noreturn __start_xen(unsigned long mbi_p)
> >>>>>             cpu_has_nx ? XENLOG_INFO : XENLOG_WARNING "Warning: ",
> >>>>>             cpu_has_nx ? "" : "not ");
> >>>>>  
> >>>>> +
> >>>>> +    printk(XENLOG_INFO
> >>>>> +           "PCID (Process-Context IDentifier) %ssupported\n",
> >>>>> +           cpu_has_pcid ? "" : "not ");
> >>>>> +
> >>>>> +    printk(XENLOG_INFO "INVPCID %ssupported\n", cpu_has_invpcid ? "" : "not ");
> >>>>
> >>>> Do we really need this? We log a message for NX as an exception,
> >>>> we don't do so for other features (and things would get pretty
> >>>> unwieldy if we did).
> >>>
> >>> I'd rather keep this message. As we are hiding PCID and INPCID from dom0
> >>> this is the only indicator of those features being supported. In case of
> >>> an error related to TLB consistency this information is important IMO.
> >> 
> >> Well, this argument would hold for almost every other advanced
> >> feature we use.
> > 
> > Then I'd suggest to either add individual messages for those features or
> > to have a single message (or a few) to list all features like the flags
> > in /proc/cpuinfo. This list could even be part of the "xl info" output.
> 
> I have no idea whether there are plans to make this part of
> "xl info" output; xen-cpuid certainly can tell you.
> 
> Wei, btw - for the case of there being problems with this new use
> of INVPCID, perhaps you will also want to extend parse_xen_cpuid()
> so that the use can be disabled from the command line.
> 

Noted.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-03-05 13:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  9:50 [PATCH 0/2] Use invpcid Wei Liu
2018-03-05  9:50 ` [PATCH 1/2] x86: report if PCID and INVPCID are supported Wei Liu
2018-03-05  9:51   ` Juergen Gross
2018-03-05 11:20   ` Jan Beulich
2018-03-05 11:31     ` Wei Liu
2018-03-05 11:48       ` Andrew Cooper
     [not found]   ` <5A9D362002000078001AE74F@suse.com>
2018-03-05 11:43     ` Juergen Gross
2018-03-05 12:37       ` Jan Beulich
     [not found]       ` <5A9D482202000078001AE7ED@suse.com>
2018-03-05 12:49         ` Juergen Gross
2018-03-05 12:57           ` Jan Beulich
2018-03-05 13:26             ` Wei Liu [this message]
2018-03-05  9:50 ` [PATCH 2/2] x86: use invpcid to do global flushing Wei Liu
2018-03-05  9:52   ` Juergen Gross
2018-03-05 11:31   ` Jan Beulich
2018-03-05 11:50     ` Andrew Cooper
2018-03-05 12:06       ` Juergen Gross
2018-03-05 12:35         ` Andrew Cooper
2018-03-05 12:54           ` Jan Beulich
2018-03-05 12:57             ` Andrew Cooper
2018-03-05 13:11               ` Juergen Gross
2018-03-05 13:24                 ` Jan Beulich
2018-03-05 13:31                   ` Wei Liu
2018-03-05 13:40                     ` Andrew Cooper
2018-03-05 13:44                     ` Jan Beulich
2018-03-06  7:10           ` Juergen Gross
2018-03-09 15:29   ` Jan Beulich
     [not found]   ` <5AA2B67302000078001B0567@suse.com>
2018-03-09 18:05     ` Juergen Gross
2018-03-12 12:59       ` Jan Beulich
2018-03-12 13:10         ` Juergen Gross
2018-03-12 13:13           ` Jan Beulich
     [not found]           ` <5AA67CEF0200007800129C5D@suse.com>
2018-03-12 13:14             ` Juergen Gross
2018-03-13  8:07           ` Jan Beulich
     [not found]           ` <5AA794B402000078001B0CC7@suse.com>
2018-03-13  9:27             ` Juergen Gross
2018-03-13  9:35               ` Jan Beulich
     [not found]               ` <5AA7A97702000078001B0D63@suse.com>
2018-03-13  9:48                 ` Juergen Gross
2018-03-13 10:22                   ` Jan Beulich
2018-03-13 10:26                     ` 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=20180305132646.762q3l55322xvi4g@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jgross@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.