From: Avi Kivity <avi@redhat.com>
To: Peter Lieven <pl@dlh.net>
Cc: Bruce Rogers <brogers@novell.com>, kvm@vger.kernel.org
Subject: Re: [stable] [PATCH 3/3][STABLE] KVM: add schedule check to napi_enable call
Date: Mon, 06 Dec 2010 18:12:20 +0200 [thread overview]
Message-ID: <4CFD0B64.3050701@redhat.com> (raw)
In-Reply-To: <DF2E57A9-5516-4CFF-A033-B588C08E19F5@dlh.net>
On 12/03/2010 05:44 PM, Peter Lieven wrote:
> Is there any reason why this patch is not yet in the stable kernel?
> virtio_net is still crashing under heavy load in current vanilla kernel.
> This patch *might be* the solution.
Perhaps some confusion. I've asked Greg to take kvm patches from
Marcelo and myself (after they've been autotested), however virtio is
not kvm, so the normal stable@ free-for-all applies.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-06 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 19:38 [PATCH 3/3][STABLE] KVM: add schedule check to napi_enable call Bruce Rogers
2010-06-03 21:03 ` [stable] " Greg KH
2010-06-03 22:17 ` Bruce Rogers
2010-06-03 22:51 ` Greg KH
2010-06-04 0:02 ` Bruce Rogers
2010-06-04 0:02 ` Bruce Rogers
2010-12-03 15:44 ` Peter Lieven
2010-12-06 16:12 ` Avi Kivity [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=4CFD0B64.3050701@redhat.com \
--to=avi@redhat.com \
--cc=brogers@novell.com \
--cc=kvm@vger.kernel.org \
--cc=pl@dlh.net \
/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