From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/2] x86: use invpcid to do global flushing
Date: Fri, 9 Mar 2018 19:05:08 +0100 [thread overview]
Message-ID: <4fb72f31-683d-1de3-db90-4788a379b0bd@suse.com> (raw)
In-Reply-To: <5AA2B67302000078001B0567@suse.com>
On 09/03/18 16:29, Jan Beulich wrote:
>>>> On 05.03.18 at 10:50, <wei.liu2@citrix.com> wrote:
>> @@ -120,11 +121,24 @@ unsigned int flush_area_local(const void *va, unsigned int flags)
>> else
>> {
>> u32 t = pre_flush();
>> - unsigned long cr4 = read_cr4();
>>
>> - write_cr4(cr4 & ~X86_CR4_PGE);
>> - barrier();
>> - write_cr4(cr4);
>> + if ( !cpu_has_invpcid )
>> + {
>> + unsigned long cr4 = read_cr4();
>> +
>> + write_cr4(cr4 & ~X86_CR4_PGE);
>> + barrier();
>> + write_cr4(cr4);
>> + }
>> + else
>> + {
>> + /*
>> + * Using invpcid to flush all mappings works
>> + * regardless of whether PCID is enabled or not.
>> + * It is faster than read-modify-write CR4.
>> + */
>> + invpcid_flush_all();
>> + }
>
> As just validly indicated by Jürgen, this is where my comment I
> gave to one of his patches actually belongs: This is correct for
> FLUSH_TLB_GLOBAL, but goes too far for FLUSH_TLB.
And again it was so even before this patch.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-09 18:05 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
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 [this message]
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=4fb72f31-683d-1de3-db90-4788a379b0bd@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=wei.liu2@citrix.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 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).