From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>, Chris Wright <chrisw@sous-sol.org>,
Arjan Koers <0h61vkll2ly8@xutrox.com>,
kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] qemu-kvm-0.13.0-rc1
Date: Mon, 13 Sep 2010 13:32:18 +0200 [thread overview]
Message-ID: <4C8E0BC2.4030500@siemens.com> (raw)
In-Reply-To: <4C8CF258.906@codemonkey.ws>
Am 12.09.2010 17:31, Anthony Liguori wrote:
> On 09/12/2010 01:11 AM, Avi Kivity wrote:
>> On 09/10/2010 10:48 PM, Anthony Liguori wrote:
>>>> I agree, is there any reason not to enable compiling less into the
>>>> binary?
>>>> There are folks interested in eliminating as much as possible to reduce
>>>> the attack surface and auditing requirements, for example.
>>>
>>> It's not a bad idea, it's just that what --disable-cpu-emulation does
>>> is evil. Being that I wrote the implementation, I'm quite confident
>>> in declare it as such :-)
>>>
>>
>> Oh, I thought you were against the idea in itself for some reason.
>>
>> I'll patch it for 0.13, but any ideas on how it should be rework for
>> master?
>
> Glauber's old Accel interface was close to the right approach. We need
> to abstract the exec.c interfaces to use a function pointer table and
> have a TCG and KVM implementation. The function pointer tables can then
> be registered by a module_init() and we can simply not include the kvm
> or TCG files are build time to disable the functionality.
Even more flexible would be to have them linked in on demand (as
specified on the command line). Additional, in certain contexts
unsupported features could then be shipped separately without having to
provide n versions of the common core. A second step to build-time
configurability, of course.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2010-09-13 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 16:29 [ANNOUNCE] qemu-kvm-0.13.0-rc1 Marcelo Tosatti
2010-09-08 20:05 ` Arjan Koers
2010-09-08 20:33 ` Anthony Liguori
2010-09-09 6:17 ` Avi Kivity
2010-09-09 13:00 ` Anthony Liguori
2010-09-10 11:47 ` Avi Kivity
2010-09-10 19:31 ` Chris Wright
2010-09-10 19:48 ` Anthony Liguori
2010-09-10 19:55 ` Chris Wright
2010-09-12 6:11 ` Avi Kivity
2010-09-12 15:31 ` Anthony Liguori
2010-09-12 15:59 ` Avi Kivity
2010-09-13 13:10 ` Glauber Costa
2010-09-13 11:32 ` Jan Kiszka [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=4C8E0BC2.4030500@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=0h61vkll2ly8@xutrox.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=kvm@vger.kernel.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