Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp980762ybe; Thu, 19 Sep 2019 06:57:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqx9U6JiJtxzT6jcNBtXQtoZm7p9bEHzCR2z72/Bb7l+YBg50rg/HUlvPyZTYHozfV1ilrW/ X-Received: by 2002:aa7:c2ce:: with SMTP id m14mr8695450edp.191.1568901432650; Thu, 19 Sep 2019 06:57:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568901432; cv=none; d=google.com; s=arc-20160816; b=I8yiO2BtjkNeLCHSapsAWT+6KCjDrznu3C6XvzgeDFQdWJ3p85s4q/1/v11F5ohp0X O+CG9rtyKJ+pMo8oG0Vg89k3s6uXHDyOLV4CchbcRKwdyGikTCNxIGyYFb27ipk/2z+O 3ELJEveH/sUveZ+oZ5AkpcCsgtoPQvQiJy+DOAmBVID39EDs3OF88RZARPFNaYRneYnM MmsVVpGw34127Q0DmYUSX6PX6IDtCwiwVAwvRdJfsXXjYcJxuWhDB8dEbP7y5j3PGqcu n3oIy6wH2FQR2y2nrVDdPI/a8jzrtncH8DYA3MZ0d37+UTE2zPo/zKgcnFr21Qt0ZgwQ x8Hw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=RpV6I9BUTkD0VxW3qJmPtG1RUVbYnAFbCt9k0EIyUBs=; b=bnHYzaTO8ZGmCl9g3aLDY/lsffznJAspv1QtUIYQEC/47Nb0paUiHx+nXo1K5AJ8Jb GgAqkbSauSCHx/6rCmdLisflMQFmnnlA9wbmoWHdywB1wQS3iv724L/CNrFMDt3FOHd9 00fkuQ7YEBSCUJ0BMwqEiR09udSSTHczVWHy2sC1U+3f7kRdT4e+hrXyZb22NPWWTzJD 3BrieLVx21oykbBkCJeqEQoFWCO/If8rmTBSxkvCDjP7lFMG5BgKMlca6fIgENkPE6zF fkUrpbQRHHF/De7e6sN0qAIhsNnLGGEPZWxfh+6l9htQvMjkZODK9l20WN37T2Hom07x 7Cpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=mwBzoNaT; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g17si4463129ejd.123.2019.09.19.06.56.49; Thu, 19 Sep 2019 06:57:12 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=mwBzoNaT; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390269AbfISNhN (ORCPT + 99 others); Thu, 19 Sep 2019 09:37:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:48056 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388819AbfISNhM (ORCPT ); Thu, 19 Sep 2019 09:37:12 -0400 Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BCC4921D80 for ; Thu, 19 Sep 2019 13:37:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568900232; bh=4h3Wk30EhI1KisIg5rn7cH+Dc4+DOKJ7JCZLxO6zmPI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=mwBzoNaTiK9xjLVihi6v8b+ryPsg0IP++84Wia1oIqwwNfxtQ14YDYKpBHJ3dYMni fBW0yG7v0NaSg/4OkKv0v7bY4ZNVgMqn10+8QuxFJes4isxMfpfRJSSSnElwMfLq/C aLk1/rm+0igwywEd+xuqNGYA8E4GRYk48izsxAtU= Received: by mail-wr1-f47.google.com with SMTP id l3so3123172wru.7 for ; Thu, 19 Sep 2019 06:37:11 -0700 (PDT) X-Gm-Message-State: APjAAAULu0WkRxvLYozpx5pa67Lqk2HZjnxzLKesQp40UCwiV6IkJo0O 4De/CxDn2tl8H4R+3BEi+nPSWoHXnjZ1sM0xPNw= X-Received: by 2002:a5d:6b49:: with SMTP id x9mr6988060wrw.80.1568900230203; Thu, 19 Sep 2019 06:37:10 -0700 (PDT) MIME-Version: 1.0 References: <20190912140256.fwbutgmadpjbjnab@willie-the-truck> <20190916181800.7lfpt3t627byoomt@willie-the-truck> In-Reply-To: From: Guo Ren Date: Thu, 19 Sep 2019 21:36:58 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH RFC 11/14] arm64: Move the ASID allocator code in a separate file To: Anup Patel Cc: Will Deacon , Palmer Dabbelt , Will Deacon , "julien.thierry@arm.com" , "aou@eecs.berkeley.edu" , "james.morse@arm.com" , Arnd Bergmann , "suzuki.poulose@arm.com" , "marc.zyngier@arm.com" , "catalin.marinas@arm.com" , "linux-kernel@vger.kernel.org" , "rppt@linux.ibm.com" , Christoph Hellwig , Atish Patra , "julien.grall@arm.com" , "gary@garyguo.net" , Paul Walmsley , "christoffer.dall@arm.com" , "linux-riscv@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "linux-arm-kernel@lists.infradead.org" , "iommu@lists.linux-foundation.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Tue, Sep 17, 2019 at 11:42 AM Anup Patel wrote: > > > > With a reply stating that the patch "absolutely does not work" ;) > > This patch was tested on existing HW (which does not have ASID implementation) > and tested on QEMU (which has very simplistic Implementation of ASID). > > When I asked Gary Guo about way to get access to their HW (in same patch > email thread), I did not get any reply. After so many months passed, I now > doubt the his comment "absolutely does not work". > > > > What exactly do you want people to do with that? It's an awful lot of effort to > > review this sort of stuff and given that Guo Ren is talking about sharing page > > tables between the CPU and an accelerator, maybe you're better off > > stabilising Linux for the platforms that you can actually test rather than > > getting so far ahead of yourselves that you end up with a bunch of wasted > > work on patches that probably won't get merged any time soon. > > The intention of the ASID patch was to encourage RISC-V implementations > having ASID in HW and also ensure that things don't break on existing HW. > > I don't see our efforts being wasted in trying to make Linux RISC-V feature > complete and encouraging more feature rich RISC-V CPUs. > > Delays in merging patches are fine as long as people have something to try > on their RISC-V CPU implementations. > I'm the supporter of that patch: http://archive.lwn.net:8080/linux-kernel/20190329045111.14040-1-anup.patel@wdc.com/T/#u Because it implicit hw broadcast tlb invalidation optimization. Honestly it's not suitable for remote tlb flush with software IPI, but it's still much better than current RISC-V's. I'll try it on our hardware: 910. wait a moment :) -- Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/