mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: jeremy@xensource.com, greg@kroah.com, zach@vmware.com,
	linux-kernel@vger.kernel.org, torvalds@osdl.org,
	hch@infradead.org, jlo@vmware.com, xen-devel@lists.xensource.com,
	simon@xensource.com, ian.pratt@xensource.com, jeremy@goop.org
Subject: Re: A proposal - binary
Date: Fri, 04 Aug 2006 18:29:14 +1000	[thread overview]
Message-ID: <1154680155.11382.84.camel@localhost.localdomain> (raw)
In-Reply-To: <20060804002107.c0f9ba25.akpm@osdl.org>

On Fri, 2006-08-04 at 00:21 -0700, Andrew Morton wrote:
> On Fri, 04 Aug 2006 17:04:59 +1000
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> > On Thu, 2006-08-03 at 22:53 -0700, Andrew Morton wrote:
> > > VMI is being proposed as an appropriate way to connect Linux to Xen.  If
> > > that is true then no other glue is needed.
> > 
> > Sorry, this is wrong.
> 
> It's actually 100% correct.

Err, yes.  I actually misrepresented VMI: the native implementation is
inline (ie. no blob is required for native).  Bad Rusty.

> > > > Yes, we could force native and Xen to work via VMI, but the result would
> > > > be less clear, less maintainable, and gratuitously different from
> > > > elsewhere in the kernel.
> > > 
> > > I suspect others would disagree with that.  We're at the stage of needing
> > > to see code to settle this.
> > 
> > Wrong again.
> 
> I was referring to the VMI-for-Xen code.

I know.  And I repeat, we don't have to see that part, to know that the
result is less clear, less maintainable and gratuitously different from
elsewhere in the kernel than the paravirt_ops approach.  We've seen
paravirt and the VMI parts of this already.

> >  We've *seen* the code for VMI, and fairly hairy.
> 
> I probably slept through that discussion - I don't recall that things were
> that bad.   Do you recall the Subject: or date?

Read the patches which Zach sent back in March, particularly:

[RFC, PATCH 3/24] i386 Vmi interface definition
[RFC, PATCH 4/24] i386 Vmi inline implementation
[RFC, PATCH 5/24] i386 Vmi code patching

If you want to hack on x86 arch code, you'd need to understand these.

Then to see the paravirt patches go to http://ozlabs.org/~rusty/paravirt
and look at the approximately-equivalent paravirt_ops patches:

	008-paravirt-structure.patch
	009-binary-patch.patch

There's nothing in those paravirt_ops patches which will surprise any
kernel hacker.  That's my entire point: maintainable, unsurprising,
clear.

Rusty.
-- 
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law


  reply	other threads:[~2006-08-04  8:29 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 10:14 Zachary Amsden
2006-08-03 11:16 ` Arjan van de Ven
2006-08-03 12:16   ` Antonio Vargas
2006-08-03 15:17     ` Rik van Riel
2006-08-03 16:05     ` Chris Wright
2006-08-03 17:57     ` Zachary Amsden
2006-08-03 18:29       ` Antonio Vargas
2006-08-03 18:47         ` Zachary Amsden
2006-08-03 18:08   ` Zachary Amsden
2006-08-03 19:03     ` Greg KH
2006-08-03 19:14       ` Zachary Amsden
2006-08-03 19:36         ` Greg KH
2006-08-03 19:56           ` Dave Jones
2006-08-03 19:59             ` Greg KH
2006-08-03 20:25             ` Options depending on STANDALONE Adrian Bunk
2006-08-03 20:28               ` Greg KH
2006-08-03 20:41                 ` Dave Jones
2006-08-03 23:40               ` [v4l-dvb-maintainer] " Trent Piepho
2006-08-05 10:51                 ` Adrian Bunk
2006-08-06 11:18                   ` Oliver Endriss
2006-08-13 16:36                     ` Adrian Bunk
2006-08-14 21:15                       ` Trent Piepho
2006-08-27 21:45                         ` Adrian Bunk
2006-08-03 19:48     ` A proposal - binary linux-os (Dick Johnson)
2006-08-04  6:13       ` Jan Engelhardt
2006-08-03 21:03     ` Alan Cox
2006-08-03 13:21 ` Alan Cox
2006-08-03 20:29   ` Willy Tarreau
2006-08-03 21:12     ` Alan Cox
2006-08-03 21:27       ` Zachary Amsden
2006-08-03 15:35 ` Rik van Riel
2006-08-03 18:36   ` Zachary Amsden
2006-08-05 10:45     ` Pavel Machek
2006-08-06 22:45       ` Zachary Amsden
2006-08-06 22:59         ` Greg KH
2006-08-08  0:12         ` Pavel Machek
2006-08-08  0:42           ` Zachary Amsden
2006-08-09  7:43             ` Pavel Machek
2006-08-03 19:06 ` Greg KH
2006-08-03 19:26   ` Zachary Amsden
2006-08-03 20:01     ` Greg KH
2006-08-03 21:41       ` Zachary Amsden
2006-08-03 22:33         ` Alan Cox
2006-08-03 22:30           ` Greg KH
2006-08-03 22:49             ` Zachary Amsden
2006-08-03 22:31           ` Zachary Amsden
2006-08-03 23:30             ` Alan Cox
2006-08-03 23:40               ` Zachary Amsden
2006-08-04 10:21                 ` Alan Cox
2006-08-04 14:34                   ` Theodore Tso
2006-08-05  0:06                     ` Paul Mackerras
2006-08-04  8:56         ` Christoph Hellwig
2006-08-04  2:52       ` Jeremy Fitzhardinge
2006-08-04  4:18         ` Andrew Morton
2006-08-04  5:04           ` Rusty Russell
2006-08-04  5:53             ` Andrew Morton
2006-08-04  7:04               ` Rusty Russell
2006-08-04  7:21                 ` Andrew Morton
2006-08-04  8:29                   ` Rusty Russell [this message]
2006-08-04 16:57                 ` David Lang
2006-08-04 18:38                   ` Jeremy Fitzhardinge
2006-08-04 18:46                   ` Antonio Vargas
2006-08-04 19:06                     ` David Lang
2006-08-04 19:26                       ` Arjan van de Ven
2006-08-04 19:45                         ` David Lang
2006-08-04 20:11                           ` Jeremy Fitzhardinge
2006-08-04 20:31                             ` David Lang
2006-08-04 21:26                               ` Jeremy Fitzhardinge
2006-08-04 21:40                                 ` Bill Rugolsky Jr.
2006-08-04 22:00                           ` Arjan van de Ven
2006-08-04 22:45                             ` David Lang
2006-08-04 19:45                       ` Jeff Dike
2006-08-04 19:49                         ` David Lang
2006-08-04 21:46                           ` Jeff Dike
2006-08-04 22:40                             ` David Lang
2006-08-04  5:40           ` Chris Wright
2006-08-04  6:28             ` Antonio Vargas
2006-08-04  7:01               ` Chris Wright
2006-08-04  7:19                 ` Antonio Vargas
2006-08-04  7:37                   ` Chris Wright
2006-08-04 18:34       ` Chris Wright
2006-08-04 20:41         ` Zachary Amsden
2006-08-04 20:52           ` Chris Wright
2006-08-04 21:26           ` Alan Cox
2006-08-05  1:14             ` James Bottomley
2006-08-05  5:37               ` Zachary Amsden
2006-08-05 10:42                 ` Adrian Bunk
2006-08-05 11:50                 ` Alan Cox
2006-08-04 22:01           ` Andi Kleen
2006-08-04 22:39             ` Zachary Amsden
2006-08-04 22:52               ` Andi Kleen
2006-08-04 22:43             ` David Lang
2006-08-05 10:47             ` Adrian Bunk
2006-08-05 11:57               ` Andi Kleen
2006-08-05  1:30           ` James Bottomley
2006-08-05  4:33             ` 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=1154680155.11382.84.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=ian.pratt@xensource.com \
    --cc=jeremy@goop.org \
    --cc=jeremy@xensource.com \
    --cc=jlo@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simon@xensource.com \
    --cc=torvalds@osdl.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=zach@vmware.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

Powered by JetHome