From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gildas <gildas.ml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: kvm-37 confusion
Date: Wed, 12 Sep 2007 11:07:06 +0300 [thread overview]
Message-ID: <46E79E2A.60402@qumranet.com> (raw)
In-Reply-To: <b2ace7f20709110258yc62103v8eff09f74688a88a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Gildas wrote:
> Hi all,
>
> It seems there was a lot of regressions on kvm-37. I've tried to
> follow the different patches and problem but the situation is full of
> confusion it seems.
>
Sure, the lapic merge is large and complex. Some confusion is to be
expected.
> Perhaps there is the need for another release including the patches
> that are thought to fix the problem some of us have experienced? It
> would be easier to spot what's working and what's not.
>
kvm-38 will be released shortly and I'll keep a short release cycle
until things stabilize.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-12 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 9:58 kvm-37 confusion Gildas
[not found] ` <b2ace7f20709110258yc62103v8eff09f74688a88a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-12 8:07 ` Avi Kivity [this message]
[not found] ` <46E79E2A.60402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 8:13 ` Dong, Eddie
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=46E79E2A.60402@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gildas.ml-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox