From: Anthony Liguori <aliguori@us.ibm.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Andi Kleen <ak@suse.de>,
Xen-devel <xen-devel@lists.xensource.com>,
Wim Coekaerts <wim.coekaerts@oracle.com>,
Chris Wright <chrisw@osdl.org>,
Christopher Li <chrisl@vmware.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, Linus Torvalds <torvalds@osdl.org>,
Anne Holler <anne@vmware.com>, Jan Beulich <jbeulich@novell.com>,
Jyothy Reddy <jreddy@vmware.com>, Kip Macy <kmacy@fsmware.com>,
Ky Srinivasan <ksrinivasan@novell.com>,
Leendert van Doorn <leendert@watson.ibm.com>
Subject: Re: [RFC, PATCH 5/24] i386 Vmi code patching
Date: Wed, 22 Mar 2006 18:31:00 -0600 [thread overview]
Message-ID: <4421EC44.7010500@us.ibm.com> (raw)
In-Reply-To: <20060322214025.GJ15997@sorel.sous-sol.org>
Chris Wright wrote:
> * Andi Kleen (ak@suse.de) wrote:
>
>> The disassembly stuff indeed doesn't look like something
>> that belongs in the kernel.
>>
>
> Strongly agreed. The strict ABI requirements put forth here are not
> in-line with Linux, IMO. I think source compatibility is the limit of
> reasonable, and any ROM code be in-tree if something like this were to
> be viable upstream.
>
Hi Chris,
Would you have less trouble if the "ROM" were actually more like a
module? Specifically, if it had a proper elf header and symbol table,
used symbols as entry points, and was a GPL interface (so that ROM's had
to be GPL)? Then it's just a kernel module that's hidden in the option
ROM space and has a C interface.
I know you end up losing the ability to do crazy inlining of the ROM
code but I think it becomes a much less hairy interface that way.
Regards,
Anthony Liguori
> thanks,
> -chris
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/virtualization
>
next prev parent reply other threads:[~2006-03-23 0:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 18:02 [RFC, PATCH 5/24] i386 Vmi code patching Zachary Amsden
2006-03-13 18:02 ` Zachary Amsden
2006-03-15 10:02 ` Chris Wright
2006-03-15 16:01 ` Zachary Amsden
2006-03-15 22:05 ` Anthony Liguori
2006-03-15 23:00 ` Pavel Machek
2006-03-17 0:51 ` Zachary Amsden
2006-03-17 10:08 ` Joshua LeVasseur
2006-03-17 21:11 ` Chris Wright
2006-03-18 0:49 ` Joshua LeVasseur
2006-03-16 19:10 ` Jan Engelhardt
2006-03-16 19:45 ` Rik van Riel
2006-03-16 21:54 ` Zachary Amsden
2006-03-22 20:15 ` Andi Kleen
2006-03-22 21:40 ` Chris Wright
2006-03-22 22:16 ` Zachary Amsden
2006-03-22 22:33 ` Daniel Arai
2006-03-22 23:02 ` Chris Wright
2006-03-22 22:51 ` Chris Wright
2006-03-22 23:36 ` Zachary Amsden
2006-03-23 0:41 ` Chris Wright
2006-03-23 0:54 ` Zachary Amsden
2006-03-23 1:06 ` Chris Wright
2006-03-23 4:04 ` Zachary Amsden
2006-03-23 11:42 ` Joshua LeVasseur
2006-03-23 0:31 ` Anthony Liguori [this message]
2006-03-23 0:40 ` Chris Wright
2006-03-23 0:40 ` Chris Wright
2006-03-23 9:25 ` Keir Fraser
2006-03-23 9:25 ` Keir Fraser
2006-03-23 18:50 ` [Xen-devel] " Zachary Amsden
2006-03-23 18:50 ` Zachary Amsden
2006-03-23 23:45 ` [Xen-devel] " Eli Collins
2006-03-23 23:45 ` Eli Collins
2006-03-24 3:26 ` Stefan Berger
2006-03-23 0:46 ` [Xen-devel] " Zachary Amsden
2006-03-23 0:46 ` Zachary Amsden
2006-03-23 0:53 ` [Xen-devel] " Anthony Liguori
2006-03-23 0:53 ` Anthony Liguori
2006-03-23 1:01 ` [Xen-devel] " Zachary Amsden
2006-03-23 1:01 ` Zachary Amsden
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 23:41 Volkmar Uhlig
2006-03-28 0:52 Chuck Ebbert
2006-03-28 1:48 ` Zachary Amsden
2006-03-28 1:48 ` Zachary Amsden
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=4421EC44.7010500@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=ak@suse.de \
--cc=anne@vmware.com \
--cc=chrisl@vmware.com \
--cc=chrisw@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jbeulich@novell.com \
--cc=jreddy@vmware.com \
--cc=kmacy@fsmware.com \
--cc=ksrinivasan@novell.com \
--cc=leendert@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=virtualization@lists.osdl.org \
--cc=wim.coekaerts@oracle.com \
--cc=xen-devel@lists.xensource.com \
/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.