From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 448DDC77B7C for ; Wed, 24 May 2023 16:02:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238244AbjEXQCn (ORCPT ); Wed, 24 May 2023 12:02:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55144 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238189AbjEXQC1 (ORCPT ); Wed, 24 May 2023 12:02:27 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5B8F01BD; Wed, 24 May 2023 09:01:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1684944074; x=1716480074; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Wx0Ob/xebu07nSB9TJ+GF90jaV0TCKSH0UQ2GQEg59o=; b=RETM/931CbERbzpPgwOiAxqENRCG6p7YFd+3qZK3xafr2DYmDHgCYLWa 0GDfBegkWSZ35HQmC+hp1f740bFgVV8JA5yQjIqIyD+wDXFOyxiGjPprV W/Bz5TQYN4iqxGY3igo6Pvf8OuG7EmivcnaLJ5/PkwFJ0mLwS7VU1RDpX J5a7zx613HNYITxTngezU0hqENZVtNsUd0Ehzk2z9qgxJILJBhLT3vho8 Uld5PPSQPIAQY4H4/rwIDJwuzul+TG2rBfVIGttw6pRcrAttVXuR9+YzO g3VZkFLtza/k5iwl/RhEq955M0XZfmymdJXJXx8hd5X6rw5ZP3RmVF2NF g==; X-IronPort-AV: E=McAfee;i="6600,9927,10720"; a="343073976" X-IronPort-AV: E=Sophos;i="6.00,189,1681196400"; d="scan'208";a="343073976" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 May 2023 08:59:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10720"; a="654853056" X-IronPort-AV: E=Sophos;i="6.00,189,1681196400"; d="scan'208";a="654853056" Received: from kknopp-mobl1.amr.corp.intel.com (HELO [10.212.186.147]) ([10.212.186.147]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 May 2023 08:59:44 -0700 Message-ID: <571c2a4a-4832-e64e-4f3c-8e7c8a795579@intel.com> Date: Wed, 24 May 2023 09:00:12 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH] x86/pci/xen: populate MSI sysfs entries Content-Language: en-US To: Juergen Gross , Maximilian Heyne , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , xen-devel@lists.xenproject.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Ashok Raj , Greg Kroah-Hartman , Marc Zyngier , "Ahmed S. Darwish" , Kevin Tian , Jason Gunthorpe , Bjorn Helgaas References: <20230503131656.15928-1-mheyne@amazon.de> <20230524154330.GA52988@dev-dsk-mheyne-1b-c1362c4d.eu-west-1.amazon.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/24/23 08:47, Juergen Gross wrote: >> Any other feedback on this one? This is definitely a bug but I >> understand that >> there might be different ways to fix it. > > I'd be happy to take the patch via the Xen tree, but I think x86 > maintainers should at least ack that. Ack. Works for me.