From: Helge Deller <deller@gmx.de>
To: John David Anglin <dave.anglin@bell.net>,
linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH][RFC] parisc: Use local tlb purges only on UP machines
Date: Sun, 25 Sep 2022 20:58:36 +0200 [thread overview]
Message-ID: <114efb2d-7f09-6a80-43d7-2a132146774f@gmx.de> (raw)
In-Reply-To: <e2ffc031-0e62-8e2b-82eb-aac0460a453c@bell.net>
On 9/25/22 20:44, John David Anglin wrote:
> On 2022-09-25 2:19 p.m., John David Anglin wrote:
>>> One goal of that patch was to drop the CONFIG_PA20 ifdef case,
>>> because a 32-bit kernel could be compiled for PA8000 in which case
>>> the "pdtlb,l" will burn the machine.
>> Don't think so. "pdtlb,l" is available on all PA 2.0 machines. It's not 64-bit specific.
> There is some difference in implementation between PA 1.1 and 2.0. 64-bit register
> values are used in the PA 2.0 implementation.
That's right.
But if you build a 32-bit kernel and choose to optimize for PA8x00 CPUs,
the CONFIG_PA20 is set and the local-purge is used unconditionally.
That breaks e.g. when running such a kernel in qemu (which is 32-bit only).
See my just-posted patch.
Helge
next prev parent reply other threads:[~2022-09-25 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 6:56 [PATCH][RFC] parisc: Use local tlb purges only on UP machines Helge Deller
2022-09-25 14:33 ` John David Anglin
2022-09-25 17:51 ` Helge Deller
2022-09-25 18:19 ` John David Anglin
2022-09-25 18:44 ` John David Anglin
2022-09-25 18:58 ` Helge Deller [this message]
2022-09-25 19:27 ` John David Anglin
2022-09-25 20:00 ` Helge Deller
2022-09-25 20:21 ` 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=114efb2d-7f09-6a80-43d7-2a132146774f@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--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 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 NNTP newsgroup(s).