From: Vineet Gupta <vgupta@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Vineet Gupta <vgupta@kernel.org>
Cc: linux-snps-arc@lists.infradead.org, rppt@kernel.org, willy@infradead.org
Subject: Re: [PATCH] ARC: mm: retire support for aliasing VIPT D$
Date: Mon, 14 Aug 2023 12:45:59 -0700 [thread overview]
Message-ID: <e7063cb9-ca5d-39db-099e-70a0889499c1@kernel.org> (raw)
In-Reply-To: <20230814123822.f117e89873c9bfc62ed0df33@linux-foundation.org>
On 8/14/23 12:38, Andrew Morton wrote:
> On Sun, 13 Aug 2023 12:25:43 -0700 Vineet Gupta <vgupta@kernel.org> wrote:
>
>> Legacy ARC700 processors (first generation of MMU enabled ARC cores) has
>> VIPT cached which could be configured such that they could alias.
>> I added the VIPT aliasing support, with all the cache flush overhead to
>> support all but 1 silicon. That is long bygone and we can remove the
>> complexity and maintenance burden of that unneeded code.
>>
>> This also helps streamline support for new features such as generic folio
>> work.
>>
> This of course messes up Matthew's "arc: implement the new page table
> range API". Are you or Matthew up for redoing that patch?
>
> Alternatively, can you redo this patch on top of Matthew's patch (ie,
> against mm-unstable or linux-next)?
Yeah I'll let Matthew's code get merged and redo mine once that is
upstream to avoid conflicts in transition.
Thx,
-Vineet
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2023-08-14 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 19:25 [PATCH] ARC: mm: retire support for aliasing VIPT D$ Vineet Gupta
2023-08-14 19:38 ` Andrew Morton
2023-08-14 19:45 ` Vineet Gupta [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7063cb9-ca5d-39db-099e-70a0889499c1@kernel.org \
--to=vgupta@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=rppt@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).