From: Avi Kivity <avi@qumranet.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: "Hesse, Christian" <mail@earthworm.de>,
kvm-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [ANNOUNCE] kvm howto
Date: Thu, 02 Nov 2006 17:19:23 +0200 [thread overview]
Message-ID: <454A0C7B.4080701@qumranet.com> (raw)
In-Reply-To: <aec7e5c30611020714qe6bcc41ucc789e3a2ca85c1f@mail.gmail.com>
Magnus Damm wrote:
>>
>> You need a newer binutils. I'm using binutils-2.16.91.0.6 (gotta love
>> that version number), shipped with Fedora Core 5.
>
> The VT-extensions added by Intel and AMD only adds a limited number of
> instructions each. If you want to be user friendly it might be a good
> idea to implement these instructions as macros. I'm pretty sure
> VT-extension support in Xen works with my old binutils version.
>
Yes, Xen uses macros.
I figured a newish machine will have a newish binutils. Looks like I
was wrong. I don't like uglifying the code, but if many users hit this,
there won't be much of a choice.
[A minor problem with macros is that you can't let gcc choose the
registers for you with instructions that have operands]
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-11-02 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 13:25 [ANNOUNCE] kvm howto Avi Kivity
2006-11-02 14:27 ` Hesse, Christian
2006-11-02 14:32 ` Avi Kivity
2006-11-02 15:14 ` Magnus Damm
2006-11-02 15:19 ` Avi Kivity [this message]
2006-11-05 17:14 ` Tomasz Torcz
2006-11-06 8:15 ` Dor Laor
2006-11-13 20:34 ` overriding BIOS (was: Re: [ANNOUNCE] kvm howto) Tomasz Torcz
2006-11-13 20:39 ` Arjan van de Ven
2006-11-06 8:51 ` [ANNOUNCE] kvm howto Avi Kivity
2006-11-06 10:14 ` Arjan van de Ven
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=454A0C7B.4080701@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mail@earthworm.de \
/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