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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 681A7C3DA60 for ; Thu, 18 Jul 2024 13:20:21 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id EF1E86B0088; Thu, 18 Jul 2024 09:20:20 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EA1B36B0089; Thu, 18 Jul 2024 09:20:20 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D90C06B0092; Thu, 18 Jul 2024 09:20:20 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id BB3226B0088 for ; Thu, 18 Jul 2024 09:20:20 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 34E30A080A for ; Thu, 18 Jul 2024 13:20:20 +0000 (UTC) X-FDA: 82352932200.30.961D33B Received: from greygoose-centos7.csh.rit.edu (greygoose-centos7.csh.rit.edu [129.21.49.170]) by imf27.hostedemail.com (Postfix) with ESMTP id 2163C4002B for ; Thu, 18 Jul 2024 13:20:17 +0000 (UTC) Authentication-Results: imf27.hostedemail.com; dkim=none; spf=none (imf27.hostedemail.com: domain of mstrodl@freedom.csh.rit.edu has no SPF policy when checking 129.21.49.170) smtp.mailfrom=mstrodl@freedom.csh.rit.edu; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=rit.edu (policy=quarantine) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1721308786; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=64GmzFHVhshnDLdp4lGFbRC9R50S0Z9LTpBEc2j+S2Q=; b=tL7KBK0TRuDZ5X8hg+1yPVJhUJIKM79/30KyaIg2RMBRbiKigS+Mh8fg/iORHKdoIKpkbu zZDQfVrH31npjVqTsoDiGQwvAZrmMt07Y4Ld7LBJb7rjQulwhYd/zEtLHApQKhgrXaiPLs aHI18U7cSCwhzj+IAaZ/XwvCvwYL5xo= ARC-Authentication-Results: i=1; imf27.hostedemail.com; dkim=none; spf=none (imf27.hostedemail.com: domain of mstrodl@freedom.csh.rit.edu has no SPF policy when checking 129.21.49.170) smtp.mailfrom=mstrodl@freedom.csh.rit.edu; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=rit.edu (policy=quarantine) ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1721308786; a=rsa-sha256; cv=none; b=LTleAjJJvxzAoBrxuScKp7YrqDNkXiXgqiqnVrVWJOoEpMnWwlHn6/6L+STRbvbM+Yu27j dzcGgJSG6rA3E7/od/rXACE/+EmAUtNMMc1Fcfxz1IeFcXqInLwjI0/H27b4qPJ6hlFbSe 1XgO49kGbI4A7lRASQ5iVD8vf+NLpoU= Received: from localhost (localhost [127.0.0.1]) by greygoose-centos7.csh.rit.edu (Postfix) with ESMTP id 22C2240D7C8B; Thu, 18 Jul 2024 09:20:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at csh.rit.edu Received: from greygoose-centos7.csh.rit.edu ([127.0.0.1]) by localhost (mail.csh.rit.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4FOPOOqDHB88; Thu, 18 Jul 2024 09:20:16 -0400 (EDT) Received: from freedom.csh.rit.edu (freedom.csh.rit.edu [129.21.49.182]) by greygoose-centos7.csh.rit.edu (Postfix) with ESMTPS id 6884B45735E9; Thu, 18 Jul 2024 09:20:16 -0400 (EDT) Date: Thu, 18 Jul 2024 09:20:15 -0400 From: Mary Strodl To: Matthew Wilcox Cc: Christoph Hellwig , Mary Strodl , linux-kernel@vger.kernel.org, akpm@linux-foundation.org, urezki@gmail.com, linux-mm@kvack.org, lee@kernel.org, andi.shyti@kernel.org, linux-i2c@vger.kernel.org, s.hauer@pengutronix.de, christian.gmeiner@gmail.com Subject: Re: [PATCH 1/3] mm: vmalloc: export __vmalloc_node_range Message-ID: References: <20240718011504.4106163-1-mstrodl@csh.rit.edu> <20240718011504.4106163-2-mstrodl@csh.rit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: w147xfzkqudhdrmuqz736k5j7spjrnkc X-Rspam-User: X-Rspamd-Queue-Id: 2163C4002B X-Rspamd-Pre-Result: action=add header; module=dmarc; Action set by DMARC X-Rspamd-Server: rspam02 X-Rspam: Yes X-HE-Tag: 1721308817-567472 X-HE-Meta: U2FsdGVkX1+8TNJ64mxZLCJBati5QEvjAK223QyIjGhap2YDuaml0GvXhZnIiJwHsxR2uegDgbhoH0RC5STqKvyxf1dUHcA2BSwrur5/9T9dCjnm2TJo8niXbHfrtNStEBGlZ8JYqHangGliYSXszuxhw1SI75BztAtgGB2jd9guvnAoqOs2x3BLrhYNgqfO3ksU3Sz6qEUdWbTHpGuYHYHq684B32ISmd5lebeChKBWwsajpy0vz05IMpH9mkgoG5h0VDlLee4+4SB0TeuuzCimXvv++LOAK+PqsqnyQwv0QC5WatD0wKX1DATax8r7PF6JfYo/a1Ra/h/W/GYH1s25d7eAKTBqgtk1WISOf55wGbBakO1HuwzBRfOZyunp2kWj2/c0nXyuaEJD4Ey/gSojvKBb95kTaGnp1vqNZkyyJmAKmmdNsNlAD8APwe9yfVVSc5ANEoXBbM0Ql95tCRGrvWRuad1d+rtCJTTjr90EaaXbXyCkEB4QmYswrxyoN3nbxqXRn2ZkfcgiWe0wbjVcCAPP8785d2ZsS8Yudm+cX5slRbjZ50ZpFB0s/riaUvSiAtgUOArosMpTuoGPtyJZ4QBzOJSuVPHrwggMzTpNU6a1mIWUyg3bCH2UruqMQFvTCg9wpi2AJZW/m8DWAvaIs2BYLQ9OHSQTqcgTfB25QKVS2ohueEOi0iskxzElK0Ep6F4qLLd6b1qmm5rgMPP9Hpawmo1JCwCpqQfRZG4UqpGzLlC1gbiAVfn8u+bGY/LSVHLYDyWr2fRkDHfDlDLxWedTy3LWaUaT/gwyKJ3/KvU2NYicvlH3OhvgxSi8Kq+/tKzo7+KBWaWdgf5ks/nSX5MQ6h19hSHEgpJul6+VuIv0bzEEAEKIKPG2kAhHOoepN+CLjZWPLKePNVfacFhmRKCg4mvKeX+sjfLiasXCLACM1y/yIrphQhYdkGr/JV5HkBvW8b1dZrsmHpP qVXc01i7 JTs3dpU+ON3+g4kgK0vPA1CYk+sWCJczpU1X05NGjB47T8DvnsYWskdJIOqP7yB4apz4ECv17YcTpN1clcPJ9doIxrKvjE17cQX86mnaR5mJUSaRIwCLqiMGl6NuP4lCzdDxRGxjGqD3hkTJrLegieGQcmxQOF9Jhv6vda24FFKMP+lVI3Ygwbfq1MC53DFs4hwpmEWSjz8PcGnaQ+SSLh/GNLs4Mu64pyFYtfl9sHe53glBrnLz3l4uo0X9tOyTe/IQY X-Bogosity: Ham, tests=bogofilter, spamicity=0.000004, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Thu, Jul 18, 2024 at 01:53:23PM +0100, Matthew Wilcox wrote: > That does work, but I would assume that since this BIOS exists to > communicate with the hardware that it'd need various special privileges > and that running in ring 3 would not work. Exactly. > Ultimately, better off running the whole thing inside a VM and passing > the device through to the guest. Or ignoring the BIOS entirely and > implementing direct access to the hardware. But neither of these > approaches is "a way to do what I'm trying to do", they're entirely > different approaches to making this hardware work. If I ran the whole thing inside a VM, I would still need support in the kernel, right? As far as I know, there is no documentation on Congatec's side about the underlying interface. Obviously I could disassemble the blob in the BIOS and figure it out, but I suspect that will have much less hardware compatibility and be subject to random breakage if they make a BIOS update or something. Plus, I would probably run afoul of copyright if I wrote a driver after doing that. I'm not really thrilled that this is their design either, but I'm not sure that there is a better answer... Thank you!