From: Adrian Bunk <bunk@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tobias Powalowski <t.powa@gmx.de>, Takashi Iwai <tiwai@suse.de>,
Christoph Hellwig <hch@infradead.org>,
Zachary Amsden <zach@vmware.com>
Subject: Re: [PATCH] x86/paravirt: revert exports to restore old behaviour
Date: Wed, 28 Nov 2007 21:40:50 +0100 [thread overview]
Message-ID: <20071128204050.GA29463@stusta.de> (raw)
In-Reply-To: <474CA0DA.3010005@goop.org>
On Tue, Nov 27, 2007 at 02:57:30PM -0800, Jeremy Fitzhardinge wrote:
>...
> Christoph Hellwig objects to this patch on the grounds that modules
> shouldn't be using these operations anyway. I don't think this is a
> particularly good reason to reject the patch, for several reasons:
>
> 1. These operations are still available to modules when not using
> CONFIG_PARAVIRT, since they are implicitly exported as inline
> functions via the kernel headers. Exporting the same functionality as
> GPL-only symbols just adds a gratuitious difference between
> CONFIG_PARAVIRT and non-CONFIG_PARAVIRT configurations. If we really
> think these operations are not for module use (or non-GPL module use),
> then we should solve the problem in a general way.
Current practice in the kernel is that when something that should not be
done works by chance with some kernel versions and/or configurations
that's simply an unfortunate fact that should be fixed but doesn't
result in any guarantee that it works with all kernel versions and/or
configurations.
> 2. It's a regression from previous kernels, which would work these
> modules even with CONFIG_PARAVIRT enabled.
>...
It cannot be a regression since the kernel does not have a stable API
for modules.
> Therefore, I think this patch should go in for 2.6.24. If people
> really think that these operations should not be available to modules,
> then we can address that separately.
>...
Why should we start with one step back for getting two steps ahead?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-11-28 20:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 22:57 [PATCH] x86/paravirt: revert exports to restore old behaviour Jeremy Fitzhardinge
2007-11-28 20:40 ` Adrian Bunk [this message]
2007-11-28 21:15 ` Jeremy Fitzhardinge
2007-11-28 22:39 ` Adrian Bunk
2007-11-28 23:57 ` Jeremy Fitzhardinge
2007-11-29 22:06 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2007-11-13 10:39 REGRESSION: 2.6.24 breaks nvidia and amd/ati binary drivers, by exporting paravirt symbols as GPL Tobias Powalowski
2007-11-13 20:21 ` [PATCH] x86/paravirt: revert exports to restore old behaviour Jeremy Fitzhardinge
2007-11-13 22:22 ` Christoph Hellwig
2007-11-14 0:51 ` Zachary Amsden
2007-11-19 17:05 ` Takashi Iwai
2007-11-20 1:14 ` Jeremy Fitzhardinge
2007-11-20 6:25 ` Takashi Iwai
2007-11-14 1:22 ` Jeremy Fitzhardinge
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=20071128204050.GA29463@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t.powa@gmx.de \
--cc=tiwai@suse.de \
--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