From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0012F380FEC for ; Fri, 29 May 2026 17:21:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780075264; cv=none; b=i4FM0ELyamELuYBmlQkVKTtSt5KpoNYHCLh2cf72xl6TSDs3k5PCd3CZY08XZpGZO6ETW3ezdnUSBxcW/3WbN6KPTFzoOeJSPX3QENBzymuungqWbZReIg6k/u9OItDcyHaEWpH3njuyDbve1YtH6fw3ylFZMY/4Neaf9y4Kvzs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780075264; c=relaxed/simple; bh=KtFcn/QJBRCbw2WF0UzyYL7p1sBdtTgiOFGIBUVca0w=; h=Message-ID:Date:MIME-Version:To:Cc:References:Subject:From: In-Reply-To:Content-Type; b=LatCJYkGv7h04HqtnRcQ8TsNg2X3l6WimWaJoXBtkXmYdXvB4z3qnEwGskvdEsElOJ/BxO7R9w5925VE0fLpB9n9dRoh9W07ErVT5oWfkYDyVpGM9e8/7NtSM7T2ghhdwrdS2xWvWMIIo3x4wSFxaGEfjyY1NWBQtJFrymXdqws= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=WoC2kghi; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="WoC2kghi" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1780075259; h=from:from:reply-to: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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=y8xWKvxO5SSqF5Z76veqmFt7SrbWGs9L9IueFeKNqAg=; b=WoC2kghiKnrqHgTPSXGLThg1SJTz/Ecg9nqLH+NQrJm+9mFln00IsmK+3YK/jEZd5w7bhp I0GHsdsx9REv1trKu+mV0OsYudvFhzScIoiU1FWirxHctkVguIOhoG0yP1xY9SWajtLU3g 4L9u/zFthqmlouaLdVyeaUkUOjdo+tI= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-125-xazLv_AyOZGN8s7UERz5MA-1; Fri, 29 May 2026 13:20:56 -0400 X-MC-Unique: xazLv_AyOZGN8s7UERz5MA-1 X-Mimecast-MFC-AGG-ID: xazLv_AyOZGN8s7UERz5MA_1780075254 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 38BE118005B2; Fri, 29 May 2026 17:20:53 +0000 (UTC) Received: from [10.22.65.177] (unknown [10.22.65.177]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id C1DA61800465; Fri, 29 May 2026 17:20:48 +0000 (UTC) Message-ID: <05290c17-d55f-4e60-a77e-c36c3f14a89a@redhat.com> Date: Fri, 29 May 2026 13:20:48 -0400 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: cmirabil@redhat.com Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, haxel@fzi.de, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, namcao@linutronix.de, palmer@dabbelt.com, pjw@kernel.org, vitaly.wool@konsulko.com, Kunwu Chan , Zhouyi Zhou zhou , igor.b@beldev.am, Jisheng Zhang , Albert Ou , Frederik Haxel , charlie@rivosinc.com References: Subject: Re: [PATCH] riscv: Remove support for XIP kernel Content-Language: en-US Reply-To: CABe3_aH6jYyoC=Jx91qATP2kOoY42NUtesyZpGbWGoQTw75OAA@mail.gmail.com From: Jesse Taube-Perrotta In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 > It is true, though I would like it to continue to be possible > upstream. When I wrote this I didn't realize that XIP is currently not > compatible with M-mode linux. I think that would be a really useful > combination that might actually make XIP something that people > se/test since both m-mode / nommu linux and xip are more common in > embedded usecases. IIRC there was a patch that made XIP work on M-mode no-mmu linux for only 64bit. I unfortunately missed this email, i should check the mailing list folder more, but I am one of the few people that is interested in XIP riscv linux, quite a few of my personal projects use it. My interest is mostly in the no-mmu rv32 use case. I'm curious if re-adding back XIP,  or i guess just adding, XIP to no-mmu rv32 would be acceptable as I have some patches that have been in the works sense 2024 LMFAO. I now have a job at redhat so maintaining XIP risc-v is a genuine possibility especially as I have quite a bit of experience with it. Ironically charlie sits near me in the office. Hi charlie! > I was hoping to develop patches for that functionality too and prove > that it works on real hardware. But in order to do that I would need > to figure out m-mode linux on unleashed/qemu sifive_u (almost > certainly possible, but I haven't really tested it) and also XIP linux > on unleased/sifive_u (which as I said is close, but with at least one > more issue) and then combine them simultaneously (unclear how hard > lol). I also have hardware and a FPGA soft-core i can test this on. TLDR: Is re-adding XIP to no-mmu rv32 a possibility Sorry if i messed up the reply i just setup this email client. Thanks, Jesse Taube