linux-kernel - Re: [PATCH 1/2] x86, Kconfig: Move PARAVIRT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130125092032.GC31478@gmail.com>
Date:	Fri, 25 Jan 2013 10:20:32 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
	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, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH 1/2] x86, Kconfig: Move PARAVIRT_DEBUG into the paravirt
 menu


* Borislav Petkov <bp@...en8.de> wrote:

> On Fri, Jan 25, 2013 at 09:21:26AM +0100, Ingo Molnar wrote:
> > 
> > So, these two patches, on top of -tip, produce:
> > 
> > vmw_balloon.c:(.init.text+0x8506): undefined reference to `x86_hyper'
> > vmw_balloon.c:(.init.text+0x850a): undefined reference to `x86_hyper_vmware'
> 
> Hmm, I somehow can't trigger it here. And the thing is, vmw_balloon.c is
> built only when CONFIG_VMWARE_BALLOON is set and that is not the case in
> this config.
> 
> [ ??? ]

Maybe it's related, but I had to resolve two conflicts when 
merging your two patches to tip:x86/cpu and then to tip:master - 
first in arch/x86/Kconfig, then in 
arch/x86/include/asm/hypervisor.h.

The second conflict looked harmless, due to:

  4cca6ea04d31 x86/apic: Allow x2apic without IR on VMware platform

Thanks,

	Ingo
--
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/