From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>, kvm@vger.kernel.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"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: Tue, 24 Jan 2017 11:36:39 +0000 [thread overview]
Message-ID: <15d06a81-28bf-7fd9-ce4b-d3d07383e8b4@users.sourceforge.net> (raw)
In-Reply-To: <1485224105.31460.1.camel@petrovitsch.priv.at>
>> Would others like to help in approaches for checking corresponding
>> run time changes a bit more?
>
> You propose the patch
I suggested additional changes which can get an usual mixture of agreements
and rejections.
> and others should do the work to get it accepted?
Not directly. - I imagine that there are further collaboration possibilities,
aren't there?
Which benchmarks (and test metrics) would you trust for the desired software evolution?
Regards,
Markus
prev parent reply other threads:[~2017-01-24 11:36 UTC|newest]
Thread overview: 18+ 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: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:12 ` [PATCH 2/9] KVM: Move error code settings in kvm_vm_ioctl() 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:14 ` [PATCH 4/9] KVM: Move error code settings in kvm_vcpu_ioctl() SF Markus Elfring
2017-01-22 18:15 ` [PATCH 5/9] KVM: Improve size determinations " 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: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:18 ` [PATCH 8/9] KVM: Adjust seven checks for null pointers SF Markus Elfring
2017-01-22 20:32 ` kbuild test robot
2017-01-22 21:35 ` kbuild test robot
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-23 9:22 ` [PATCH 0/9] KVM: Fine-tuning for several function implementations Paolo Bonzini
2017-01-23 9:48 ` SF Markus Elfring
2017-01-23 14:06 ` Paolo Bonzini
2017-01-24 2:15 ` Bernd Petrovitsch
2017-01-24 11:36 ` SF Markus Elfring [this message]
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=15d06a81-28bf-7fd9-ce4b-d3d07383e8b4@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=bernd@petrovitsch.priv.at \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox