From: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH/RFC] Let gcc to choose which registers to save
Date: Mon, 22 Oct 2007 17:34:01 +0200 [thread overview]
Message-ID: <471CC2E9.4010109@bull.net> (raw)
In-Reply-To: <471CC1F2.6040002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity a écrit :
> Laurent Vivier wrote:
>>
>>> Other than that the patch is very welcome -- the excessive register
>>> saving is very annoying to me.
>>>
>>
>> I think we can do the same thing with svm.c, but I can't test it.
>>
>>
>
> I can test it for you (but a separate patch please -- these are likely
> to cause trouble with different compilers and options, so I want them to
> be easy to revert).
>
>
OK, thank you
Laurent
--
---------------- Laurent.Vivier-6ktuUTfB/bM@public.gmane.org -----------------
"Given enough eyeballs, all bugs are shallow" E. S. Raymond
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-22 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 14:51 [PATCH/RFC] Let gcc to choose which registers to save Laurent Vivier
[not found] ` <11930647183090-git-send-email-Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
2007-10-22 15:10 ` Avi Kivity
[not found] ` <471CBD5D.9040506-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 15:24 ` Laurent Vivier
[not found] ` <471CC0B7.204-6ktuUTfB/bM@public.gmane.org>
2007-10-22 15:29 ` Avi Kivity
[not found] ` <471CC1F2.6040002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 15:34 ` Laurent Vivier [this message]
2007-10-27 11:12 ` Alexander Graf
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=471CC2E9.4010109@bull.net \
--to=laurent.vivier-6ktuutfb/bm@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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.