From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: KVM 32bit support broken in SVN?
Date: Thu, 15 Feb 2007 14:13:34 +0200 [thread overview]
Message-ID: <45D44E6E.308@qumranet.com> (raw)
In-Reply-To: <45D12F77.8040503-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Anthony Liguori wrote:
> I've been tracking down a rather strange SEGV in SVN. I'm on a 32bit
> SVM system. I think people are seeing the same on 32bit VMX.
>
> Basically, we get to the first EINTR returned by kvm_run(). Everything
> goes as expected until we get to cpu_loop_exit(). When we get to this
> point, the jmp_buf appears to be invalid as the longjmp() goes off into
> a bad high address.
>
> Still trying to track down but wanted to share what I've found.
>
>
This is now fixed (or rather worked around, as the fix changes libkvm.a
where it shouldn't).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-02-15 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 3:24 KVM 32bit support broken in SVN? Anthony Liguori
[not found] ` <45D12F77.8040503-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-02-13 14:20 ` Daniel Hecken
2007-02-15 10:41 ` Avi Kivity
2007-02-15 12:13 ` 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=45D44E6E.308@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@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