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 BB063C7EE29 for ; Fri, 9 Jun 2023 15:32:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241439AbjFIPce (ORCPT ); Fri, 9 Jun 2023 11:32:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60626 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232202AbjFIPcd (ORCPT ); Fri, 9 Jun 2023 11:32:33 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D63A23596 for ; Fri, 9 Jun 2023 08:32:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1686324748; x=1717860748; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=v51RHSTw8xEjQxppc1XRi8stX/tlHpxTk03qUolx73Y=; b=Mq9O4tqkAzCmTj7rhN5nQ9WG5kP0gxT8mOd1UQLQX3pZSfMYJnhZIg99 TwN4oUgnIVxLajlby0kIDCSMYwsmAHMFS6PyhWxVmyLVZL2cs6+AEZ0Jj pHM0yAh0vGMCrJqn+f8KjEsYbp8+GvPZthtAcYX38plEEELETUMDwjdY2 rS/AHiEpM08jgFb40TIbx+op3R2lNvF3Ngd7gjKvQgVXB59D7fdruzOB5 M3rMXuTtm4OYrK9IWVFmfYxOk5uCy+aC2M1CBaS+wsXJSKUCFjMQ6VDwE wHB3pl76fg8+pOo1aTPu89DyQu8CImFNDMU0wzbIDx3wo2110TZQiRrOw w==; X-IronPort-AV: E=McAfee;i="6600,9927,10736"; a="385988578" X-IronPort-AV: E=Sophos;i="6.00,229,1681196400"; d="scan'208";a="385988578" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jun 2023 08:32:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10736"; a="884633183" X-IronPort-AV: E=Sophos;i="6.00,229,1681196400"; d="scan'208";a="884633183" Received: from mdeisher-mobl3.amr.corp.intel.com (HELO [10.212.149.144]) ([10.212.149.144]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jun 2023 08:32:23 -0700 Message-ID: <74ec3164-1d1d-7546-6008-9d028354e50a@intel.com> Date: Fri, 9 Jun 2023 08:32:23 -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 v3] iscsi_ibft: Fix finding the iBFT under Xen Dom 0 Content-Language: en-US To: konrad@darnok.org, Juergen Gross Cc: Ross Lagerwall , LKML , xen-devel@lists.xenproject.org, Jan Beulich , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , X86 ML , Boris Ostrovsky , Peter Jones , Konrad Rzeszutek Wilk References: <20230605102840.1521549-1-ross.lagerwall@citrix.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 6/9/23 08:22, Konrad Rzeszutek Wilk wrote: > Dave, are you OK with the change in where the reserve call is made? The move makes logical sense. I'm not 100% confident it won't regress anything, but the blast radius should be limited to iSCSI. But, yeah, I'm OK with it.