Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp731343rwd; Wed, 7 Jun 2023 06:16:20 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5VOyhYl37UQYCPrNVM2/FTwodWjCDgrSwiB6YboZ7voSkZvhVdqjxxQbAxhQTFHDz1LUA1 X-Received: by 2002:a17:90a:1016:b0:24d:ef23:fe28 with SMTP id b22-20020a17090a101600b0024def23fe28mr2664325pja.49.1686143780260; Wed, 07 Jun 2023 06:16:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686143780; cv=none; d=google.com; s=arc-20160816; b=g29mYGQS6A25l1E2EdINLDS1AkCZ/l1momU5JKC5nAcN/YnsSTG4hu2bouf6oyftF4 at4keo/FIn6I7ONadjq1xkRu5uDl8eIZh14X7RlkhiLLfJVPDADYK5xaG7a5SnUbx5db 4YJtP8HqdbYjwm/fMrNJECpF2lOOzWx3ij8Xy7nxGiNaF3KgKB1v+H6roEuKWY9kCK9G CMi6gfraQvvXIevnwLIjcf0tAKJcZQEAWRrBjakalpmieHvoLUx07OgLZb6E1tDJttdi 8GgUfVdRv+ge4JK3zCa+XBlr8GD8TOAxuDmpkLJVbSWIWAEGwv8oJ/5u1NFPx5tixxFq YOSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=LJTxKG2Vp02RuH0gWwrDnc+jFT706OI0Ii0rwRRyaR0=; b=fS9y0upqffGgTDRBWusPg29V9QPEiHZspW0dlA5SFyIqI3dUmYIr8YPVEUMrP8vFWY z+F3/cXZCaVvTHnySRpDbheq4U8OoQGzEX1I18JK5yeJ4tQd7loYBGKqtism4Tibgc/w WrBR4HDPdiPPzWvxqiG4E8tMyJnopaUcckfp1PzJtFzVr0U8ITOS8fb282wrQ9a8ywFl x9KYVm7guXXuy0n9Rz7Ny7ZEkhyccjEjn4hS0HZScOWovfl2RIlCnKdk0dtTNb2JFqOa jjn6GtimX2GXeVOga12O/KJ4wp6xgvmVelmzSKYTFgZ6Te6yneeu+g28ZdmKHeHYEBIq I7DA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h8-20020a17090a604800b0024df598ed11si1092580pjm.188.2023.06.07.06.16.06; Wed, 07 Jun 2023 06:16:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240029AbjFGNNH (ORCPT + 99 others); Wed, 7 Jun 2023 09:13:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235792AbjFGNNC (ORCPT ); Wed, 7 Jun 2023 09:13:02 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D0F0795 for ; Wed, 7 Jun 2023 06:13:01 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 33B3F6732D; Wed, 7 Jun 2023 15:12:58 +0200 (CEST) Date: Wed, 7 Jun 2023 15:12:57 +0200 From: Christoph Hellwig To: Juergen Gross Cc: Marek =?iso-8859-1?Q?Marczykowski-G=F3recki?= , Christoph Hellwig , Stefano Stabellini , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Ben Skeggs , Karol Herbst , Lyude Paul , xen-devel@lists.xenproject.org, iommu@lists.linux.dev, linux-kernel@vger.kernel.org, nouveau@lists.freedesktop.org Subject: Re: [PATCH 2/4] x86: always initialize xen-swiotlb when xen-pcifront is enabling Message-ID: <20230607131257.GB19206@lst.de> References: <20230518134253.909623-1-hch@lst.de> <20230518134253.909623-3-hch@lst.de> <20230519040405.GA10818@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 22, 2023 at 10:37:09AM +0200, Juergen Gross wrote: > In normal cases PCI passthrough in PV guests requires to start the guest > with e820_host=1. So it should be rather easy to limit allocating the > 64MB in PV guests to the cases where the memory map has non-RAM regions > especially in the first 1MB of the memory. > > This will cover even hotplug cases. The only case not covered would be a > guest started with e820_host=1 even if no PCI passthrough was planned. > But this should be rather rare (at least I hope so). So is this an ACK for the patch and can we go ahead with it? (I'd still like to merge swiotlb-xen into swiotlb eventually, but it's probably not going to happen this merge window)