From: "Jan Beulich" <JBeulich@suse.com> To: Paul Durrant <paul.durrant@citrix.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>, george.dunlap@citrix.com, Roger Pau Monne <roger.pau@citrix.com> Subject: Re: [PATCH 4/9] x86/HVM: move NOFLUSH handling out of hvm_set_cr3() Date: Thu, 02 May 2019 07:23:00 -0600 [thread overview] Message-ID: <5CCAEF34020000780022B400@prv1-mh.provo.novell.com> (raw) In-Reply-To: <42621a15169c4a409efa29e3d2d7e06e@AMSPEX02CL03.citrite.net> >>> On 02.05.19 at 15:07, <Paul.Durrant@citrix.com> wrote: >> From: Jan Beulich [mailto:JBeulich@suse.com] >> Sent: 02 May 2019 13:20 >> >> --- a/xen/arch/x86/hvm/emulate.c >> +++ b/xen/arch/x86/hvm/emulate.c >> @@ -2072,6 +2072,8 @@ static int hvmemul_write_cr( >> HVMTRACE_LONG_2D(CR_WRITE, reg, TRC_PAR_LONG(val)); >> switch ( reg ) >> { >> + bool noflush; >> + > > Why introduce 'noflush' with this scope when it could be limited to 'case > 3:', although... Because this would entail introducing another set of braces, and I pretty much dislike these case-block braces: They either don't properly indent (as we do commonly), or they needlessly increase indentation of the enclosed block. Hence my general preference of switch-scope local variables. >> @@ -2082,7 +2084,10 @@ static int hvmemul_write_cr( >> break; >> >> case 3: >> - rc = hvm_set_cr3(val, true); >> + noflush = hvm_pcid_enabled(current) && (val & X86_CR3_NOFLUSH); >> + if ( noflush ) >> + val &= ~X86_CR3_NOFLUSH; > > ... can't you just code this as: > > if ( hvm_pcid_enabled(current) ) > val &= ~X86_CR3_NOFLUSH; > > ? Because of ... >> + rc = hvm_set_cr3(val, noflush, true); ... this further use of "noflush" (alongside the adjusted "val"). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Jan Beulich" <JBeulich@suse.com> To: "Paul Durrant" <paul.durrant@citrix.com> Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel <xen-devel@lists.xenproject.org>, Wei Liu <wei.liu2@citrix.com>, george.dunlap@citrix.com, Roger Pau Monne <roger.pau@citrix.com> Subject: Re: [Xen-devel] [PATCH 4/9] x86/HVM: move NOFLUSH handling out of hvm_set_cr3() Date: Thu, 02 May 2019 07:23:00 -0600 [thread overview] Message-ID: <5CCAEF34020000780022B400@prv1-mh.provo.novell.com> (raw) Message-ID: <20190502132300.WWoerdmIxLEbmPSWbcQcdiERuM96_8hp0UPXa4kVNYQ@z> (raw) In-Reply-To: <42621a15169c4a409efa29e3d2d7e06e@AMSPEX02CL03.citrite.net> >>> On 02.05.19 at 15:07, <Paul.Durrant@citrix.com> wrote: >> From: Jan Beulich [mailto:JBeulich@suse.com] >> Sent: 02 May 2019 13:20 >> >> --- a/xen/arch/x86/hvm/emulate.c >> +++ b/xen/arch/x86/hvm/emulate.c >> @@ -2072,6 +2072,8 @@ static int hvmemul_write_cr( >> HVMTRACE_LONG_2D(CR_WRITE, reg, TRC_PAR_LONG(val)); >> switch ( reg ) >> { >> + bool noflush; >> + > > Why introduce 'noflush' with this scope when it could be limited to 'case > 3:', although... Because this would entail introducing another set of braces, and I pretty much dislike these case-block braces: They either don't properly indent (as we do commonly), or they needlessly increase indentation of the enclosed block. Hence my general preference of switch-scope local variables. >> @@ -2082,7 +2084,10 @@ static int hvmemul_write_cr( >> break; >> >> case 3: >> - rc = hvm_set_cr3(val, true); >> + noflush = hvm_pcid_enabled(current) && (val & X86_CR3_NOFLUSH); >> + if ( noflush ) >> + val &= ~X86_CR3_NOFLUSH; > > ... can't you just code this as: > > if ( hvm_pcid_enabled(current) ) > val &= ~X86_CR3_NOFLUSH; > > ? Because of ... >> + rc = hvm_set_cr3(val, noflush, true); ... this further use of "noflush" (alongside the adjusted "val"). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-02 13:23 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-02 11:35 [PATCH 0/9] XSA-292 follow-up Jan Beulich 2019-05-02 11:35 ` [Xen-devel] " Jan Beulich 2019-05-02 12:18 ` [PATCH 1/9] x86: adjust cr3_pcid() return type Jan Beulich 2019-05-02 12:18 ` [Xen-devel] " Jan Beulich 2019-05-02 12:19 ` [PATCH 2/9] x86: limit the amount of TLB flushing in switch_cr3_cr4() Jan Beulich 2019-05-02 12:19 ` [Xen-devel] " Jan Beulich 2019-05-02 12:19 ` [PATCH 3/9] x86/mm: honor opt_pcid also for 32-bit PV domains Jan Beulich 2019-05-02 12:19 ` [Xen-devel] " Jan Beulich 2019-05-02 12:20 ` [PATCH 4/9] x86/HVM: move NOFLUSH handling out of hvm_set_cr3() Jan Beulich 2019-05-02 12:20 ` [Xen-devel] " Jan Beulich 2019-05-02 13:07 ` Paul Durrant 2019-05-02 13:07 ` [Xen-devel] " Paul Durrant 2019-05-02 13:23 ` Jan Beulich [this message] 2019-05-02 13:23 ` Jan Beulich 2019-05-02 13:25 ` Paul Durrant 2019-05-02 13:25 ` [Xen-devel] " Paul Durrant 2019-05-02 12:20 ` [PATCH 5/9] x86/HVM: refuse CR3 loads with reserved (upper) bits set Jan Beulich 2019-05-02 12:20 ` [Xen-devel] " Jan Beulich 2019-05-02 12:21 ` [PATCH 6/9] x86/HVM: relax shadow mode check in hvm_set_cr3() Jan Beulich 2019-05-02 12:21 ` [Xen-devel] " Jan Beulich 2019-05-02 12:21 ` [PATCH 7/9] x86/HVM: cosmetics to hvm_set_cr3() Jan Beulich 2019-05-02 12:21 ` [Xen-devel] " Jan Beulich 2019-05-02 12:22 ` [PATCH 8/9] x86/CPUID: drop INVPCID dependency on PCID Jan Beulich 2019-05-02 12:22 ` [Xen-devel] " Jan Beulich 2019-05-02 12:22 ` [PATCH 9/9] x86: PCID is unused when !PV Jan Beulich 2019-05-02 12:22 ` [Xen-devel] " 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=5CCAEF34020000780022B400@prv1-mh.provo.novell.com \ --to=jbeulich@suse.com \ --cc=andrew.cooper3@citrix.com \ --cc=george.dunlap@citrix.com \ --cc=paul.durrant@citrix.com \ --cc=roger.pau@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: linkBe 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.