Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp2079254pxj; Sat, 19 Jun 2021 02:15:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzw59YbpGymno6QA0qFE/tr1OTIk9bjiPUUl+bJIRzlL9RmSa8+CrQJgWH8XsBtfAvC0bHF X-Received: by 2002:a05:6e02:f48:: with SMTP id y8mr10655983ilj.85.1624094147268; Sat, 19 Jun 2021 02:15:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624094147; cv=none; d=google.com; s=arc-20160816; b=f04Zd2AGCHIw+eJGDtAhNSR//1fO1NO0ke+1NXhWWcqh5vfP1C5tvXf3h06vrsCXT5 Ghi1Li+OmASsxCpmlV2U2m2fOZ6IRFuuJyL93h1kHQJ/ottmOo/mg/60TJNz1sUWVpak RbmbXEwkh0RnQFRlbsrWI9RT9YfvAx0rVlfDIv0NYocfDFzxCPEX39ngzyEiKoJgC+qI P0gko62IKkVhaRLwpw2K0sLDz501WiRUvtJeOPIGTI/f2yFoiMhd2QGkYGNbgZv8jQ64 eEPmWExCwMJ8ltsMBIwwn+xIEsndfFxAaNVxEQ+p2sqgWlzaB5biq6p98gQc/Zu6OY+Z peFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:message-id :mime-version:in-reply-to:references:cc:to:subject:from:date :dkim-signature; bh=6TdDLes2Gw5ionLs5FEcoq+qBpg/39isQHw8hmOU2DM=; b=bInngnOSZxnTvCyvHq7L5ZW2w7qWXkLDdeJA9BO2M+E2nJYy5WCtyksRA0iM/1H4VJ TbqtZ4Fy9/xMUqLuAseCGNL/VugrZdf/ingc8Ezuj5uwsFUbhLQMVwURmWzTXREgGwm/ 02iU9GQWcomWEQwbo8cIz0GzTMrxRHQsUt/46mdhEZ0rREpah5EZT0p/PU0djSTpQFTb o+DqodSdbAJ6unOlH11duvJF/cMlxoqrpTrdzkv1y14fFzEIyZeyrP1eCie143qXgnTF 8UhcuFInLMD3I9NIwsr2ivsejKKzx59V1KPIGAufH+qUwywMpVfS1thriqYMuhwwMSdP Ehpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DIK4FeNK; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c15si14088208jam.64.2021.06.19.02.15.27; Sat, 19 Jun 2021 02:15:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DIK4FeNK; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235603AbhFSDZA (ORCPT + 99 others); Fri, 18 Jun 2021 23:25:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234943AbhFSDZA (ORCPT ); Fri, 18 Jun 2021 23:25:00 -0400 Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 98E70C061574 for ; Fri, 18 Jun 2021 20:22:49 -0700 (PDT) Received: by mail-pj1-x102e.google.com with SMTP id l11so2484159pji.5 for ; Fri, 18 Jun 2021 20:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:references:in-reply-to:mime-version :message-id:content-transfer-encoding; bh=6TdDLes2Gw5ionLs5FEcoq+qBpg/39isQHw8hmOU2DM=; b=DIK4FeNKIz4uCyjknxXRGeur2lOR4V6Rm15a9SC3QuG8+LEAXvJu/F4FUwHaev8Yo8 ysyUTIRpWZLUXV5rhUDSGKfc0+2GSqtZkhOHf7HHmK4ijX97R3k5mkjCAtUIm/l+/CJN mOV+R1jkEWDQiyy4vqqQZXOLJQn1zQj/m9C4lXUXmNFyobuYc/T5CQ8sDPD53x8GNo+O BH9v2VW8TlG6JqB/pCd6rtoausxb04nCUwFtvVp4wDKEJoajRDyoXib/2StggY7vD86U DMWYrj19QZvxlLJ7aZQTvLrpUOueNo6HthLIfHhFbl8nTXpTvqZh8FzqX+RIoYH+EKPS JHoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to :mime-version:message-id:content-transfer-encoding; bh=6TdDLes2Gw5ionLs5FEcoq+qBpg/39isQHw8hmOU2DM=; b=dBjjGDQ3n1wTU7vUoTXRosjUPLiNtMXpN+K9tExPFpZcDG5tx4jX8cK7dHtkQXK5kv hz7Al/qDWklHUsSmDr1gbePn2sq3n3uGvZI6P2isIy5iNUrcqYH8sAd2oPJ1FqqL7Zte QO64tBCOrwlf+n5hxjML1lnuqYG/sqgBXzoR9O91BxFtUJIL7LZ32W9dlr1TlycUKvgC RHiumNssae+4/4ExBqJcIP5KS1KEVqqpOZHKXzCbpZyuT4QgKddSYKsAtfr0F6FoQQSV QVpfb+Dk2ReqbQb125teAah8k4z1eMjbblC8fSQk0skeXWwNfK9NWxzpmx5PAzJJFVtA SpUw== X-Gm-Message-State: AOAM531G5dUlqpJ/WeGUsSY04/JHpMww6xY+nbYPiZIYSb276q1WA23K 5pJgOAwP6EP8A5Z85sVkWsM= X-Received: by 2002:a17:902:6904:b029:fb:42b6:e952 with SMTP id j4-20020a1709026904b02900fb42b6e952mr7625233plk.16.1624072969252; Fri, 18 Jun 2021 20:22:49 -0700 (PDT) Received: from localhost (60-242-147-73.tpgi.com.au. [60.242.147.73]) by smtp.gmail.com with ESMTPSA id q23sm10014316pgm.31.2021.06.18.20.22.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Jun 2021 20:22:48 -0700 (PDT) Date: Sat, 19 Jun 2021 13:22:43 +1000 From: Nicholas Piggin Subject: Re: [PATCH v6 13/17] powerpc/pseries/vas: Setup IRQ and fault handling To: Haren Myneni , herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au Cc: haren@us.ibm.com, hbabu@us.ibm.com References: <827bf56dce09620ebecd8a00a5f97105187a6205.camel@linux.ibm.com> <1623972635.u8jj6g26re.astroid@bobo.none> In-Reply-To: MIME-Version: 1.0 Message-Id: <1624072930.d9ivbdzz50.astroid@bobo.none> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Excerpts from Haren Myneni's message of June 18, 2021 12:09 pm: > On Fri, 2021-06-18 at 09:34 +1000, Nicholas Piggin wrote: >> Excerpts from Haren Myneni's message of June 18, 2021 6:37 am: >> > NX generates an interrupt when sees a fault on the user space >> > buffer and the hypervisor forwards that interrupt to OS. Then >> > the kernel handles the interrupt by issuing H_GET_NX_FAULT hcall >> > to retrieve the fault CRB information. >> >=20 >> > This patch also adds changes to setup and free IRQ per each >> > window and also handles the fault by updating the CSB. >>=20 >> In as much as this pretty well corresponds to the PowerNV code >> AFAIKS, >> it looks okay to me. >>=20 >> Reviewed-by: Nicholas Piggin >>=20 >> Could you have an irq handler in your ops vector and have=20 >> the core code set up the irq and call your handler, so the Linux irq >> handling is in one place? Not something for this series, I was just >> wondering. >=20 > Not possible to have common core code for IRQ setup.=20 >=20 > PowerNV: Every VAS instance will be having IRQ and this setup will be > done during initialization (system boot). A fault FIFO will be assigned > for each instance and registered to VAS so that VAS/NX writes fault CRB > into this FIFO. =20 >=20 > PowerVM: Each window will have an IRQ and the setup will be done during > window open.=20 Yeah, I thought as much. Just wondering. Thanks, Nick