All of lore.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Helge Deller <deller@gmx.de>,
	linux-parisc <linux-parisc@vger.kernel.org>
Cc: deller@kernel.org
Subject: Re: fixmap problem on PA11 hardware
Date: Sun, 31 Oct 2021 18:47:53 -0400	[thread overview]
Message-ID: <dba5227c-0616-f51e-b716-9569304804bd@bell.net> (raw)
In-Reply-To: <0a068f90-84bb-dbe1-b8b3-6fd7709b814a@gmx.de>

Hi Helge,

My sense is the invalidate patch isn't correct.  The main difference between pdc and fdc is that
it is optional whether pdc writes the cache line back to memory when it's dirty at priority 0.

Note also that flush_kernel_vmap_range and invalidate_kernel_vmap_range both have this hunk
which may behave differently:

         if ((!IS_ENABLED(CONFIG_SMP) || !arch_irqs_disabled()) &&
             (unsigned long)size >= parisc_cache_flush_threshold) {
                 flush_tlb_kernel_range(start, end);
                 flush_data_cache();
                 return;
         }

Dave

On 2021-10-31 5:22 p.m., Helge Deller wrote:
> On 10/27/21 22:14, John David Anglin wrote:
>> On 2021-10-27 3:09 p.m., Helge Deller wrote:
>>> In the archives I found this old thread, which might be related:
>>> https://www.spinics.net/lists/linux-parisc/msg09391.html
>> These seems unlikely as both 7100LC and 7300LC are PA-RISC 1.1 processors (1.1c vs. 1.1e).  Big difference
>> seems to be cache.
> Yes, there were at least two problems.
> I just sent two patches to the list which fix the crashes.
> But FTRACE still doesn't work on PA1.x machines as expected,
> while the same code seems to work on PA2.x machines (running the same 32bit kernel).


-- 
John David Anglin  dave.anglin@bell.net


  reply	other threads:[~2021-10-31 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 19:09 fixmap problem on PA11 hardware Helge Deller
2021-10-27 20:14 ` John David Anglin
2021-10-31 21:22   ` Helge Deller
2021-10-31 22:47     ` John David Anglin [this message]
2021-10-31 23:07       ` Helge Deller
2021-10-31 23:56         ` John David Anglin
2021-11-01  0:01           ` John David Anglin
2021-11-01  0:06             ` John David Anglin
2021-11-01 18:09               ` Helge Deller
2021-11-02 21:25                 ` John David Anglin

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=dba5227c-0616-f51e-b716-9569304804bd@bell.net \
    --to=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=deller@kernel.org \
    --cc=linux-parisc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.