From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
KVM mailing list <kvm@vger.kernel.org>,
Michael Goldish <mgoldish@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Dor Laor <dlaor@redhat.com>
Subject: Re: qemu-kvm.git build problem
Date: Mon, 11 Jan 2010 12:18:01 +0200 [thread overview]
Message-ID: <4B4AFAD9.3010604@redhat.com> (raw)
In-Reply-To: <4B4AF9D2.3080100@siemens.com>
On 01/11/2010 12:13 PM, Jan Kiszka wrote:
>
> BTW, does anybody know how to back-port synchronize_srcu_expedited best?
> It looked like a simple mapping to synchronize_srcu was not sufficient
> to achieve the same performance as with the pre-srcu locking (e.g.
> guest&host stalled during guest's framebuffer setup).
>
Isn't it sufficient to backport kernel/srcu.c? I thought no sched.c
changes were necessary.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-11 10:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 18:40 qemu-kvm.git build problem Lucas Meneghel Rodrigues
2009-12-28 19:55 ` Avi Kivity
2010-01-09 5:23 ` Lucas Meneghel Rodrigues
2010-01-11 10:13 ` Jan Kiszka
2010-01-11 10:18 ` Avi Kivity [this message]
2010-01-11 10:21 ` Jan Kiszka
2010-01-12 0:23 ` Jan Kiszka
2010-01-12 0:51 ` Paul E. McKenney
2010-01-12 8:28 ` Jan Kiszka
2010-01-12 13:50 ` Paul E. McKenney
2010-01-14 0:11 ` Jan Kiszka
2010-01-14 2:13 ` Paul E. McKenney
2010-01-15 8:58 ` Jan Kiszka
2010-01-18 2:09 ` Paul E. McKenney
2010-01-14 20:02 ` Lucas Meneghel Rodrigues
2010-01-14 23:48 ` Paul E. McKenney
2010-01-15 8:56 ` Jan Kiszka
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=4B4AFAD9.3010604@redhat.com \
--to=avi@redhat.com \
--cc=dlaor@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=mgoldish@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.