mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: John David Anglin <dave.anglin@bell.net>,
	Charlie Jenkins <charlie@rivosinc.com>
Cc: David Laight <David.Laight@aculab.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Helge Deller <deller@gmx.de>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	Parisc List <linux-parisc@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 2/2] lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests
Date: Thu, 15 Feb 2024 07:22:32 -0800	[thread overview]
Message-ID: <0e4b65c8-4b22-4011-a4ff-c679f9ec05f9@roeck-us.net> (raw)
In-Reply-To: <1d5e059e-5b31-415d-ae41-593415812e94@bell.net>

On 2/14/24 19:00, John David Anglin wrote:
> On 2024-02-14 8:58 p.m., Guenter Roeck wrote:
>> Specifically: Yes, the carry/borrow bits should be restored. Question is
>> if the Linux kernel's interrupt handler doesn't restore the carry bits
>> or if the problem is on the qemu side.
> The carry/borrow bits in the PSW should be saved and restored by the save_specials
> and rest_specials macros.  They are defined in arch/parisc/include/asm/assembly.h.
> 
> However, it appears the tophys macro might clobber the carry bits before they
> are saved in intr_save.
> 

Actually, I did some logging and found that the correct carry bits do find their way
into the IPSW register in the Linux kernel. Only when userspace is back after handling
the unaligned LDD, the carry flag is always set to 1, no matter how it was set prior
to the unaligned access.

Guenter


  parent reply	other threads:[~2024-02-15 15:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 21:41 [PATCH v8 0/2] lib: checksum: Fix issues with checksum tests Charlie Jenkins
2024-02-14 21:41 ` [PATCH v8 1/2] lib: checksum: Fix type casting in checksum kunits Charlie Jenkins
2024-02-14 21:41 ` [PATCH v8 2/2] lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests Charlie Jenkins
2024-02-14 23:03   ` Guenter Roeck
2024-02-15  1:30     ` Charlie Jenkins
2024-02-15  1:58       ` Guenter Roeck
2024-02-15  3:00         ` John David Anglin
2024-02-15  3:35           ` Charlie Jenkins
2024-02-15  4:11             ` Charlie Jenkins
2024-02-15  8:56             ` Guenter Roeck
2024-02-15 15:36               ` Charlie Jenkins
2024-02-15 16:30                 ` Guenter Roeck
2024-02-15 16:51                   ` Charlie Jenkins
2024-02-15 17:13                     ` John David Anglin
2024-02-15 17:29                     ` Guenter Roeck
2024-02-15 15:22           ` Guenter Roeck [this message]
2024-02-16  5:54         ` Helge Deller
2024-02-16  5:25           ` Guenter Roeck
2024-02-16  7:31             ` Helge Deller
2024-02-16  6:58               ` Guenter Roeck
2024-02-16  6:09           ` Guenter Roeck
2024-02-16  6:13             ` Charlie Jenkins
2024-02-16 12:05               ` Helge Deller
2024-02-16 18:22           ` John David Anglin
2024-02-15 10:27     ` David Laight
2024-02-15 15:44       ` Guenter Roeck
2024-02-15 16:51         ` John David Anglin
2024-02-15 17:06           ` Guenter Roeck
2024-02-15 17:25             ` John David Anglin
2024-02-15 18:17               ` Guenter Roeck
2024-02-15 18:56                 ` John David Anglin
2024-02-15 21:00                   ` Guenter Roeck
2024-02-15 21:08                     ` John David Anglin
2024-02-15 18:42               ` Guenter Roeck
2024-02-15 19:41                 ` David Laight
2024-02-15 19:42                 ` Charlie Jenkins
2024-02-16  5:00                   ` Guenter Roeck
2024-02-15  1:24   ` Guenter Roeck

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=0e4b65c8-4b22-4011-a4ff-c679f9ec05f9@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=David.Laight@aculab.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=charlie@rivosinc.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®