qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>, Jan Kiszka <jan.kiszka@web.de>,
	Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for Feb 9
Date: Tue, 09 Feb 2010 17:32:22 +0200	[thread overview]
Message-ID: <4B718006.6090900@redhat.com> (raw)
In-Reply-To: <4B717A75.3010300@codemonkey.ws>

On 02/09/2010 05:08 PM, Anthony Liguori wrote:
>> I'm not saying we should push hpet into the kernel to save userspace 
>> coding effort; there should be an independent reason to do this.  But 
>> I don't think threading qemu is going to be anything near easy.
>
>
> It's certainly not easy but I don't think it's impossibly hard.

Not impossible - see for example the kernel, the BKL should be removed RSN.

But yes, I think RCU will simplify things for us, and we have all of 
that experience to learn from.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-02-09 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  1:28 [Qemu-devel] KVM call agenda for Feb 9 Chris Wright
2010-02-09  6:56 ` [Qemu-devel] " Avi Kivity
2010-02-09  7:16   ` Alexander Graf
2010-02-09  8:52     ` Jan Kiszka
2010-02-09 14:18       ` Anthony Liguori
2010-02-09 14:38         ` Avi Kivity
2010-02-09 15:08           ` Anthony Liguori
2010-02-09 15:32             ` Avi Kivity [this message]
2010-02-09 14:15   ` Anthony Liguori
2010-02-09 14:18   ` Avi Kivity

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=4B718006.6090900@redhat.com \
    --to=avi@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).