From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 24EB91F03C1 for ; Wed, 2 Apr 2025 12:56:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.12 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743598604; cv=none; b=V9qq4PWPYjMECIuqxLlNa4T4UTt1G+mDRvmxGzsLV9oqeLQ9hRoSAj2cbbsS56fcF8two2IlPFfDK2eZRYRMWb555aBaPJ2MaR2U840IdOOtwkJAF4w/VIRNINDqVNnU4sbys8P0KwQoXl7GVGlrFIBZtmxSvUu/y+EK8a5pXMc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743598604; c=relaxed/simple; bh=FjzOvE9PaUyfXrgrVS5tNkvoFHbB1LjntcPMfhap/HA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=JnfRwoaG6UsOKWQC34VBmry2bZxmGQ0cm1Y/ruoLBBQFxX8/ZTHRQ8f8tWUTaH1WOoVzOxJv2W173ABznPvkM6AST/u6axBHqEKL2MEKyXv3/zz71okrCvwp9qOnAyb1j0qo0hfXca2AXF3hcfcGrmqMOiDjLVXOlrANNWNhd/4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=VPtvECeC; arc=none smtp.client-ip=198.175.65.12 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="VPtvECeC" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1743598604; x=1775134604; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=FjzOvE9PaUyfXrgrVS5tNkvoFHbB1LjntcPMfhap/HA=; b=VPtvECeCjrHcKZEHvVzCocg9/c8TZQNGTZhpXWAn2lbmvUXDg9PyhgOS fCp1iLixIjkaChCmPbnkqVSNunoQjtxF3x2EE/ivW5vtGzGdKYmgU3HwQ aUMgQd0rzMvSfXFnFny32tbQfT4VoO73yiShG0JXCG4V/quth7iwk35SP b0NODX8Cah0wI+Xn+RXKmQ+MtLG7R51groOiQ3wD1fEibHtaJejx5MdsR YWWmXgt9KGaJfRRo8vtgb6/49t8vtCban9CRCBTTAT2Y6EK/cPRKrh8b1 Oj7CGcMuJ8+zIdQkyX6wrF6vnn07BkhJOkbsFzJkow8KLaV6Daw/Qmc0B g==; X-CSE-ConnectionGUID: rQ7iKrFuRvS01o9ISV4JUQ== X-CSE-MsgGUID: XkBIVooeQDKXsvx9gT0sUg== X-IronPort-AV: E=McAfee;i="6700,10204,11392"; a="56335705" X-IronPort-AV: E=Sophos;i="6.15,182,1739865600"; d="scan'208";a="56335705" Received: from fmviesa003.fm.intel.com ([10.60.135.143]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2025 05:56:43 -0700 X-CSE-ConnectionGUID: p9JxLazqQLey8Qdj6oqRnQ== X-CSE-MsgGUID: Y2dyzab3Q4ScnjG1NblWbQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.15,182,1739865600"; d="scan'208";a="130804632" Received: from bergbenj-mobl1.ger.corp.intel.com (HELO localhost) ([10.245.246.73]) by fmviesa003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Apr 2025 05:56:41 -0700 From: Jani Nikula To: Jason Gunthorpe Cc: Masahiro Yamada , Linus Torvalds , Dave Airlie , dri-devel , LKML Subject: Re: [git pull] drm for 6.15-rc1 In-Reply-To: <20250401194649.GE325917@nvidia.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <87h6394i87.fsf@intel.com> <20250331133137.GA263675@nvidia.com> <87tt782htn.fsf@intel.com> <20250401191455.GC325917@nvidia.com> <877c433bys.fsf@intel.com> <20250401194649.GE325917@nvidia.com> Date: Wed, 02 Apr 2025 15:56:37 +0300 Message-ID: <87v7rm203e.fsf@intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, 01 Apr 2025, Jason Gunthorpe wrote: > On Tue, Apr 01, 2025 at 10:42:35PM +0300, Jani Nikula wrote: >> On Tue, 01 Apr 2025, Jason Gunthorpe wrote: >> > So, I'd suggest a better way to run this is first build the kernel, >> > then mine the gcc -MD output (ie stored in the .XX.cmd files) to >> > generate a list of headers that are actually part of the build, then >> > only test those. That eliminates all the kconfig problems. Opt out any >> > special headers that really have a good reason not to be stand alone. >> >> I think we'd want the drm headers pass the checks independent of configs >> (apart from CONFIG_DRM). One size doesn't fit all. > > Why? That demand is just making it impossible to make shared > infrastructure, and I don't think DRM should go off and build its own > stuff just for DRM in a way that nobody else can use it. > > If you really, really, care then you can have your makefile codegen an > "allheaders.c" that #includes drm/*.h and compile that. The v2 series [1] generalizes the header checks and it's no longer in any way dependent on DRM. For starters, each subsystem/driver needs to decide for themselves which headers are to be checked. For DRM, it's everything. Others can do as they please. And they can do so in their Makefiles depending on configs too (actually drm/xe does this). This can be expanded with more clever ways to choose the headers to check. But we have to start *somewhere*. BR, Jani. [1] https://lore.kernel.org/r/20250402124656.629226-1-jani.nikula@intel.com -- Jani Nikula, Intel