mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Jyothy Reddy <jreddy@vmware.com>,
	Christopher Li <chrisl@vmware.com>,
	Leendert van Doorn <leendert@watson.ibm.com>,
	Kip Macy <kmacy@fsmware.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Beulich <jbeulich@novell.com>, Anne Holler <anne@vmware.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	virtualization@lists.osdl.org,
	Ky Srinivasan <ksrinivasan@novell.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Wim Coekaerts <wim.coekaerts@oracle.com>
Subject: Re: [RFC, PATCH 5/24] i386 Vmi code patching
Date: Thu, 23 Mar 2006 09:25:28 +0000	[thread overview]
Message-ID: <caf37c433827769063ccb0269adbaa09@cl.cam.ac.uk> (raw)
In-Reply-To: <20060323004006.GQ15997@sorel.sous-sol.org>


On 23 Mar 2006, at 00:40, Chris Wright wrote:

>> 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.
>
> Yeah, point is the interface is normal C API, and has the similar free
> form that normal kernel API's have.

i think this sounds very sane, and an OS-specific interface shim gets 
around problems such as finding CPU-specific state -- we can get at 
smp_processor_id() just the same as the rest of the kernel, for 
example. We could extend the concept of the interface shim we already 
have -- a set of OS-specific high performance shims, plus a fallback 
OS-agnostic shim.

  -- Keir


  reply	other threads:[~2006-03-23  9:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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
2006-03-23  0:40       ` Chris Wright
2006-03-23  9:25         ` Keir Fraser [this message]
2006-03-23 18:50           ` [Xen-devel] " Zachary Amsden
2006-03-23 23:45           ` Eli Collins
2006-03-23  0:46       ` Zachary Amsden
2006-03-23  0:53         ` Anthony Liguori
2006-03-23  1:01           ` Zachary Amsden
2006-03-22 23:41 Volkmar Uhlig
2006-03-28  0:52 Chuck Ebbert
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=caf37c433827769063ccb0269adbaa09@cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=aliguori@us.ibm.com \
    --cc=anne@vmware.com \
    --cc=chrisl@vmware.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®