From: Christoph Hellwig <hch@infradead.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Gaudenz Steinlin <gaudenz@debian.org>,
linux-kernel@vger.kernel.org, 486798@bugs.debian.org,
josejx@gentoo.org
Subject: Re: [PATCH] restore export of handle_mm_fault for Mac on Linux
Date: Wed, 18 Jun 2008 08:51:31 -0400 [thread overview]
Message-ID: <20080618125131.GA2097@infradead.org> (raw)
In-Reply-To: <18521.846.628816.525787@cargo.ozlabs.ibm.com>
On Wed, Jun 18, 2008 at 10:45:02PM +1000, Paul Mackerras wrote:
> > Has been rejected a few times. An now that we actually have kvm
> > for powerpc in tree MOL should just merge with that project and
> > do the right things in tree instead of beeing a really hacky
> > module subverting the VM.
>
> We don't have KVM for the "classic" 32-bit PowerPC processors, only
> for the 44x family. And doing KVM for the classic 32-bit processors
> would probably involve just as much hackery as MOL. :)
I don't think so. Doing it properly in-tree will mean that it is
a) properly reviewed
b) means we can do the major VM bits in the kernel without these
really stupid exports
Have you looked at MOL recently? It's more than disgusting.
And in addition to these issue we do of course as policy not add
random hooks in the kernel tree for out of tree stuff. Especially
for hacks like this that don't even have the intention to get merged.
next prev parent reply other threads:[~2008-06-18 12:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 10:14 [PATCH] restore export of handle_mm_fault for Mac on Linux Gaudenz Steinlin
2008-06-18 11:49 ` Christoph Hellwig
2008-06-18 12:45 ` Paul Mackerras
2008-06-18 12:51 ` Christoph Hellwig [this message]
2008-06-19 9:59 ` Gaudenz Steinlin
2008-06-18 17:18 ` Alan Cox
2008-06-19 9:58 ` Gaudenz Steinlin
2008-06-19 10:38 ` Christoph Hellwig
2008-06-19 10:46 ` Pekka Enberg
2008-06-19 11:01 ` Greg KH
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=20080618125131.GA2097@infradead.org \
--to=hch@infradead.org \
--cc=486798@bugs.debian.org \
--cc=gaudenz@debian.org \
--cc=josejx@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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 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.