From: Brijesh Singh <brijesh.singh@amd.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: <brijesh.singh@amd.com>, <kvm@vger.kernel.org>,
<thomas.lendacky@amd.com>, <rkrcmar@redhat.com>,
<joro@8bytes.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<hpa@zytor.com>, <pbonzini@redhat.com>, <bp@suse.de>
Subject: Re: [PATCH v3] kvm: svm: Use the hardware provided GPA instead of page walk
Date: Tue, 29 Nov 2016 13:38:42 -0600 [thread overview]
Message-ID: <d72fab48-bcad-8e83-36e7-24d669003f05@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1611291915300.4358@nanos>
On 11/29/2016 12:20 PM, Thomas Gleixner wrote:
> On Tue, 29 Nov 2016, Brijesh Singh wrote:
>> --- a/arch/x86/kvm/emulate.c
>> +++ b/arch/x86/kvm/emulate.c
>> @@ -5483,3 +5483,11 @@ void emulator_writeback_register_cache(struct x86_emulate_ctxt *ctxt)
>> {
>> writeback_registers(ctxt);
>> }
>> +
>> +bool emulator_is_string_op(struct x86_emulate_ctxt *ctxt)
>> +{
>> + if (ctxt->d & String)
>> + return true;
>> +
>> + return false;
>> +}
>
> Do we really need a full function call for this simple thing? Just because
> this horrible CamelCase constant is in emulate.c?
>
> What's wrong with moving that thing into a header and make it a trivial
> inline:
>
> #define INS_STRING (1 << 13)
>
> static inline bool emulator_is_string_op(struct x86_emulate_ctxt *ctxt)
> {
> return ctxt->d & INS_STRING;
> }
>
> Hmm?
One of the recommendation from previous review feedback was to move the
check inside emulator.c. I am fine with inlining it into kvm_emulate.h
Hi Paolo,
Do you want me to spin a new version ?
-Brijesh
>
> tglx
>
next prev parent reply other threads:[~2016-11-29 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 18:01 [PATCH v3] x86: SVM: " Brijesh Singh
2016-11-29 18:01 ` [PATCH v3] kvm: svm: " Brijesh Singh
2016-11-29 18:10 ` Paolo Bonzini
2016-11-29 18:20 ` Thomas Gleixner
2016-11-29 19:38 ` Brijesh Singh [this message]
2016-12-08 14:53 ` Paolo Bonzini
2016-12-14 19:59 [PATCH v3] x86: SVM: " Brijesh Singh
2016-12-14 19:59 ` [PATCH v3] kvm: svm: " Brijesh Singh
2016-12-15 12:42 ` David Hildenbrand
2016-12-15 13:06 ` Paolo Bonzini
2016-12-15 13:09 ` David Hildenbrand
2016-12-15 13:31 ` Paolo Bonzini
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=d72fab48-bcad-8e83-36e7-24d669003f05@amd.com \
--to=brijesh.singh@amd.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®