Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760377Ab3EAW2y (ORCPT ); Wed, 1 May 2013 18:28:54 -0400 Received: from mail.skyhub.de ([78.46.96.112]:49691 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758433Ab3EAW2w (ORCPT ); Wed, 1 May 2013 18:28:52 -0400 Date: Thu, 2 May 2013 00:28:50 +0200 From: Borislav Petkov To: David Rientjes Cc: Ingo Molnar , "H. Peter Anvin" , linux-kernel@vger.kernel.org, Pekka Enberg , levinsasha928@gmail.com, mtosatti@redhat.com, tglx@linutronix.de, Borislav Petkov , fengguang.wu@intel.com, linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/urgent] x86/kconfig: Add a Kconfig shortcut for building working KVM guest kernels Message-ID: <20130501222850.GB15623@pd.tnic> References: <20130426095140.GA15361@pd.tnic> <20130501203500.GC4466@pd.tnic> <20130501211011.GD4466@pd.tnic> <20130501215604.GA15623@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1570 Lines: 38 On Wed, May 01, 2013 at 03:09:13PM -0700, David Rientjes wrote: > Unfortunately, the way you're implementing KVM_GUEST_COMMON_OPTIONS > will typically result in this if the options you "select" get new > dependencies in the future. So you'll always be updating this option > constantly with these types of problems. Ok, so let's step back a bit here: I've added this option with the idea to have it as a shortcut so that you don't go search for every commodity option when you want to boot the kernel as a kvm guest. Currently I have it in all.config when doing randconfig builds here. While I'm doing the randbuilds, why not boot it in kvm too while at it. Now, I really fail to see what you describe above to be a fairly normal use case. I'm sure you can take Kconfig and abuse it so that it screams all kinds of errors and we know select is evil and Kconfig is not perfect, etc, etc... So I'm pretty sure we won't be able to plug all holes. However, let's try to plug only those which hinder *real* usage instead of contrived stuff. So, let's start again: is this something real you're triggering with some random testing you're doing or are you simply abusing^Wexperimenting with Kconfig and staring at what breaks? 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/