From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jun Koi <junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [kvm-commits] kvm: kvmctl: create secondary vcpus
Date: Tue, 05 Jun 2007 12:18:47 +0300 [thread overview]
Message-ID: <46652A77.50209@qumranet.com> (raw)
In-Reply-To: <fdaac4d50706050149y2cb791b2ib8220dc628f2e1a0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Jun Koi wrote:
> So now we can have SMP guest with KVM? Great!
>
It's not done yet.
> One thing I dont understand: I dont see where you unlock
> vcpu[n].sipi_sem?
>
That's still cooking. I've written small pseudo apic which can issue
the sipi.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-05 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070605072901.DF7EF25016C@il.qumranet.com>
[not found] ` <20070605072901.DF7EF25016C-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-06-05 8:49 ` [kvm-commits] kvm: kvmctl: create secondary vcpus Jun Koi
[not found] ` <fdaac4d50706050149y2cb791b2ib8220dc628f2e1a0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-05 9:18 ` Avi Kivity [this message]
[not found] <20070604160414.8C1D125016C@il.qumranet.com>
[not found] ` <20070604160414.8C1D125016C-LjA0eNSCdXrQnzwC+xcbyw@public.gmane.org>
2007-06-05 2:30 ` Nguyen Anh Quynh
[not found] ` <9cde8bff0706041930q575311c1y8e8bdb61e31e42ba-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-05 7:29 ` 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=46652A77.50209@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=junkoi2004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.