[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130125190340.GC4973@pd.tnic>
Date: Fri, 25 Jan 2013 20:03:40 +0100
From: Borislav Petkov <bp@...en8.de>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>,
X86 ML <x86@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com,
jasowang@...hat.com, Thomas Gleixner <tglx@...utronix.de>,
JBeulich@...e.com, Dmitry Torokhov <dtor@...are.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>
Subject: Re: [PATCH -v2 2/2] x86: Make Linux guest support optional
On Fri, Jan 25, 2013 at 10:42:32AM -0800, Dmitry Torokhov wrote:
> No, not really as EXPORT_SYMBOL_GPL() in no way implies that the code
> using it lives in the mainline.
I didn't say that - I said "any code (proprietary included) can link to
those symbols" meaning that I cannot possibly convert proprietary code
to which I don't have access to, vs GPL code which is out there.
> Also, EXPORT_SYMBOL() does not imply that it forms an ABI and can't be
> changed ever.
And yet, I don't want to be on the receiving end of the complaints when
those do change. But that's beside the point.
So I think we're on the same page: I'll make everything using x86_hyper*
depend on CONFIG_HYPERVISOR_GUEST and all are happy.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists