From: Paolo Bonzini <pbonzini@redhat.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: KVM: Fine-tuning for several function implementations
Date: Mon, 23 Jan 2017 15:06:33 +0100 [thread overview]
Message-ID: <0fe83268-e233-557b-78b2-d34ff00a6ab3@redhat.com> (raw)
In-Reply-To: <a1a42521-ca5c-8bff-0121-d4b63fd570f3@users.sourceforge.net>
On 23/01/2017 10:48, SF Markus Elfring wrote:
>> The others are useless churn or they make the result uselessly different
>> from the rest of KVM code.
>
> I got an other view about potential benefits around the suggested movements
> for error code settings.
I'll consider them when your emails stop looking like the output a
Markov chain.
Paolo
> Would others like to help in approaches for checking corresponding run time changes
> a bit more?
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: KVM: Fine-tuning for several function implementations
Date: Mon, 23 Jan 2017 14:06:33 +0000 [thread overview]
Message-ID: <0fe83268-e233-557b-78b2-d34ff00a6ab3@redhat.com> (raw)
In-Reply-To: <a1a42521-ca5c-8bff-0121-d4b63fd570f3@users.sourceforge.net>
On 23/01/2017 10:48, SF Markus Elfring wrote:
>> The others are useless churn or they make the result uselessly different
>> from the rest of KVM code.
>
> I got an other view about potential benefits around the suggested movements
> for error code settings.
I'll consider them when your emails stop looking like the output a
Markov chain.
Paolo
> Would others like to help in approaches for checking corresponding run time changes
> a bit more?
next prev parent reply other threads:[~2017-01-23 14:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 18:09 [PATCH 0/9] KVM: Fine-tuning for several function implementations SF Markus Elfring
2017-01-22 18:09 ` SF Markus Elfring
2017-01-22 18:11 ` [PATCH 1/9] KVM: Return directly after a failed copy_from_user() in kvm_vm_compat_ioctl() SF Markus Elfring
2017-01-22 18:11 ` SF Markus Elfring
2017-01-22 18:12 ` [PATCH 2/9] KVM: Move error code settings in kvm_vm_ioctl() SF Markus Elfring
2017-01-22 18:12 ` SF Markus Elfring
2017-01-22 18:13 ` [PATCH 3/9] KVM: Move error code settings in kvm_vcpu_compat_ioctl() SF Markus Elfring
2017-01-22 18:13 ` SF Markus Elfring
2017-01-22 18:14 ` [PATCH 4/9] KVM: Move error code settings in kvm_vcpu_ioctl() SF Markus Elfring
2017-01-22 18:14 ` SF Markus Elfring
2017-01-22 18:15 ` [PATCH 5/9] KVM: Improve size determinations " SF Markus Elfring
2017-01-22 18:15 ` SF Markus Elfring
2017-01-22 18:16 ` [PATCH 6/9] KVM: Return an error code only as a constant in kvm_get_dirty_log_protect() SF Markus Elfring
2017-01-22 18:16 ` SF Markus Elfring
2017-01-22 18:17 ` [PATCH 7/9] KVM: Return an error code only as a constant in kvm_get_dirty_log() SF Markus Elfring
2017-01-22 18:17 ` SF Markus Elfring
2017-01-22 18:18 ` [PATCH 8/9] KVM: Adjust seven checks for null pointers SF Markus Elfring
2017-01-22 18:18 ` SF Markus Elfring
2017-01-22 20:32 ` kbuild test robot
2017-01-22 20:32 ` kbuild test robot
2017-01-22 21:35 ` kbuild test robot
2017-01-22 21:35 ` kbuild test robot
2017-01-23 9:30 ` Dan Carpenter
2017-01-23 9:30 ` Dan Carpenter
2017-01-22 18:19 ` [PATCH 9/9] KVM: Improve another size determination in kvm_create_vm() SF Markus Elfring
2017-01-22 18:19 ` SF Markus Elfring
2017-01-23 9:22 ` [PATCH 0/9] KVM: Fine-tuning for several function implementations Paolo Bonzini
2017-01-23 9:22 ` Paolo Bonzini
2017-01-23 9:48 ` SF Markus Elfring
2017-01-23 9:48 ` SF Markus Elfring
2017-01-23 14:06 ` Paolo Bonzini [this message]
2017-01-23 14:06 ` Paolo Bonzini
2017-01-24 2:15 ` Bernd Petrovitsch
2017-01-24 2:15 ` Bernd Petrovitsch
2017-01-24 11:36 ` SF Markus Elfring
2017-01-24 11:36 ` SF Markus Elfring
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=0fe83268-e233-557b-78b2-d34ff00a6ab3@redhat.com \
--to=pbonzini@redhat.com \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
/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.