From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gregory Haskins <ghaskins-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: lapic branch rebased and updated
Date: Tue, 19 Jun 2007 14:43:32 +0300 [thread overview]
Message-ID: <4677C164.6090403@qumranet.com> (raw)
In-Reply-To: <4677853D0200005A00026094-Igcdv/6uVdMHoYOw/+koYqIwWpluYiW7@public.gmane.org>
Gregory Haskins wrote:
> On Tue, 2007-06-19 at 13:29 +0300, Avi Kivity wrote:
>
>> Avi Kivity wrote:
>>
>>> Avi Kivity wrote:
>>>
>>>> - rebased to latest master
>>>> - added latest 6 patches from Gregory
>>>>
>>>>
>>> My AMD machine seems happy with it. I'll start picking stuff into
>>> mainline.
>>>
>>>
>> Spoke too soon. Things are broken.
>>
>>
>
> Do you mean the new patches broke it? Or that you are still seeing
> issues with the original v9 code on AMD? (Or both?)
>
>
Both, it appears. I'm merging stuff into mainline and testing as I do
it, as a way of finding out what broke and getting things done at the
same time.
--
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-19 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 11:26 lapic branch rebased and updated Gregory Haskins
[not found] ` <4677853D0200005A00026094-Igcdv/6uVdMHoYOw/+koYqIwWpluYiW7@public.gmane.org>
2007-06-19 11:43 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 9:54 Avi Kivity
[not found] ` <4677A7EA.8040402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-19 10:20 ` Avi Kivity
[not found] ` <4677AE08.7050205-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-19 10: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=4677C164.6090403@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ghaskins-Et1tbQHTxzrQT0dZR+AlfA@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