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 lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 090E1C43219 for ; Thu, 24 Nov 2022 19:19:35 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.448034.704824 (Exim 4.92) (envelope-from ) id 1oyHkk-0000pj-6C; Thu, 24 Nov 2022 19:19:18 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 448034.704824; Thu, 24 Nov 2022 19:19:18 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1oyHkk-0000pc-33; Thu, 24 Nov 2022 19:19:18 +0000 Received: by outflank-mailman (input) for mailman id 448034; Thu, 24 Nov 2022 19:19:17 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1oyHki-0000pW-RG for xen-devel@lists.xen.org; Thu, 24 Nov 2022 19:19:16 +0000 Received: from mail.xenproject.org (mail.xenproject.org [104.130.215.37]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id e158948a-6c2c-11ed-8fd2-01056ac49cbb; Thu, 24 Nov 2022 20:19:15 +0100 (CET) Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1oyHke-00042F-22; Thu, 24 Nov 2022 19:19:12 +0000 Received: from [54.239.6.186] (helo=[192.168.1.238]) by xenbits.xenproject.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oyHkd-0007XS-RR; Thu, 24 Nov 2022 19:19:11 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: e158948a-6c2c-11ed-8fd2-01056ac49cbb DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xen.org; s=20200302mail; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: References:Cc:To:From:Subject:MIME-Version:Date:Message-ID; bh=7LkqjOngDsmt1vHQJQpK0c7MEk/z00Zc1oBFYxn4XeU=; b=62EHk/powPg0zY7vML0SxCL9MJ S5yl1Rk3ZSEbAExowDDgGp0Mn7u/1toaQS4m1Vn4qE5NSp3EGvrboVbEwY5pOg776gYKuJpMkzFDu oAGLWiJFrscHowwgBPPnovjVD1CNB+Z+l0zdLSTg2q4uKxKQzh+V82rHPtHtwsfLmRN0=; Message-ID: <4bb29058-3133-bc66-ea33-8077f91a473b@xen.org> Date: Thu, 24 Nov 2022 20:19:09 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH V6.1 3/3] libxl: arm: make creation of iommu node independent of disk device Content-Language: en-US From: Julien Grall To: Viresh Kumar , Anthony PERARD Cc: xen-devel@lists.xen.org, Vincent Guittot , stratos-dev@op-lists.linaro.org, =?UTF-8?Q?Alex_Benn=c3=a9e?= , Stefano Stabellini , Mathieu Poirier , Mike Holmes , Oleksandr Tyshchenko , Wei Liu , Juergen Gross References: <099616e1092409fceea4eb30590215310f8c091c.1662626550.git.viresh.kumar@linaro.org> <20220920102915.p55lt4ee5hbxiun2@vireshk-i7> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Viresh, On 04/10/2022 11:59, Julien Grall wrote: > On 20/09/2022 11:29, Viresh Kumar wrote: >> On 09-09-22, 16:02, Anthony PERARD wrote: >>> On Fri, Sep 09, 2022 at 08:13:28PM +0530, Viresh Kumar wrote: >>>> The iommu node will be required for other virtio device types too, not >>>> just disk device. >>>> >>>> Move the call to make_xen_iommu_node(), out of the disk device specific >>>> block and rename "iommu_created" variable to "iommu_needed", and set it >>>> to true for virtio disk device. >>>> >>>> Signed-off-by: Viresh Kumar >>> >>> Reviewed-by: Anthony PERARD >> >> I don't see these patches being applied yet, do I need to ping someone >> for that ? > > We are currently preparing to release Xen 4.17 (plan for November) and > have stopped accepting new code (other than bug fix) since the beginning > of September. > > Your series will be committed once the tree is re-opened (hopefully by > the beginning of November). Please ping me mid-november if this is still > not applied. Unfortunately, we had some delay for releasing 4.17. So I have pushed this series in a branch for-next/4.18. This will be applied to staging once the tree has re-opened. Cheers, -- Julien Grall