From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Clean up and extend rate-limited output
Date: Mon, 12 Sep 2011 09:42:42 -0300 [thread overview]
Message-ID: <20110912124242.GB14651@amt.cnet> (raw)
In-Reply-To: <4E6DD03E.5010503@siemens.com>
On Mon, Sep 12, 2011 at 11:26:22AM +0200, Jan Kiszka wrote:
> The use of printk_ratelimit is discouraged, replace it with
> pr*_ratelimited or __ratelimit. While at it, convert remaining
> guest-triggerable printks to rate-limited variants.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> arch/x86/kvm/i8259.c | 15 ++++++++-------
> arch/x86/kvm/mmu_audit.c | 6 +++---
> arch/x86/kvm/vmx.c | 13 ++++++-------
> include/linux/kvm_host.h | 8 +++-----
> 4 files changed, 20 insertions(+), 22 deletions(-)
Applied all, thanks.
prev parent reply other threads:[~2011-09-12 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 9:26 [PATCH] KVM: Clean up and extend rate-limited output Jan Kiszka
2011-09-12 12:42 ` Marcelo Tosatti [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=20110912124242.GB14651@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.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