From: Avi Kivity <avi@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
linux-kernel@vger.kernel.org
Subject: Re: Does CONFIG_PARAVIRT imply usage of byte locks?
Date: Mon, 12 Jan 2009 09:14:49 +0200 [thread overview]
Message-ID: <496AEDE9.9000403@redhat.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0901112350580.5377@jikos.suse.cz>
Jiri Kosina wrote:
> Avi, are there any plans to make KVM use byte locks implementation for
> spinlocks in the near future?
>
No, although I note anything coming out of the spinning mutex discussion
could be applied towards a sleeping spinlock for paravirt.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-01-12 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 21:58 Does CONFIG_PARAVIRT imply usage of byte locks? Jiri Kosina
2009-01-09 22:24 ` Jiri Kosina
2009-01-10 23:53 ` Jeremy Fitzhardinge
2009-01-11 22:52 ` Jiri Kosina
2009-01-12 7:14 ` 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=496AEDE9.9000403@redhat.com \
--to=avi@redhat.com \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@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