From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org,
David Abdurachmanov <david.abdurachmanov@gmail.com>
Subject: Re: Random memory corruption with v5.2
Date: Wed, 31 Jul 2019 09:39:10 +0200 [thread overview]
Message-ID: <mvmo91a8xgh.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1907301709510.4874@viisi.sifive.com> (Paul Walmsley's message of "Tue, 30 Jul 2019 17:22:01 -0700 (PDT)")
On Jul 30 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> - Commit bf587caae305ae3b4393077fb22c98478ee55755 ("riscv: mm: synchronize
> MMU after pte change")
That would be my favorite.
> - Commit 6dd91e0eacff0a5c822ca37565d6b5740c4d2a80 ("RISC-V: defconfig:
> Enable NO_HZ_IDLE and HIGH_RES_TIMERS")
I had these enabled forever already.
> - Commit 671f9a3e2e24cdeb2d2856abee7422f093e23e29 ("RISC-V: Setup initial
> page tables in two stages")
I don't think a one-time initial setup can have such a subtle effect.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-07-31 7:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 10:51 Random memory corruption with v5.2 Andreas Schwab
2019-07-29 22:58 ` David Abdurachmanov
2019-07-30 4:27 ` Atish Patra
2019-07-30 6:56 ` Andreas Schwab
2019-07-31 0:22 ` Paul Walmsley
2019-07-31 7:39 ` Andreas Schwab [this message]
2019-07-31 8:14 ` Anup Patel
2019-08-01 19:57 ` Palmer Dabbelt
2019-07-31 10:19 ` Andreas Schwab
2019-07-31 12:57 ` Troy Benjegerdes
2019-07-31 13:10 ` Andreas Schwab
2019-08-01 18:32 ` Andreas Schwab
2019-08-02 2:00 ` Palmer Dabbelt
2019-08-02 2:15 ` Anup Patel
2019-08-05 14:08 ` Andreas Schwab
2019-08-05 14:34 ` Andreas Schwab
2019-08-05 15:36 ` Andreas Schwab
2019-08-05 22:34 ` Atish Patra
2019-08-06 0:25 ` Troy Benjegerdes
2019-08-06 0:30 ` Atish Patra
2019-08-06 6:41 ` Andreas Schwab
2019-08-06 7:43 ` Andreas Schwab
2019-08-02 7:25 ` Paul Walmsley
2019-08-02 12:08 ` Andreas Schwab
2019-08-02 17:32 ` Paul Walmsley
2019-08-05 7:13 ` Andreas Schwab
2019-08-15 20:52 ` Atish Patra
2019-08-16 5:22 ` Atish Patra
2019-08-16 15:38 ` Troy Benjegerdes
2019-08-19 10:53 ` Andreas Schwab
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=mvmo91a8xgh.fsf@suse.de \
--to=schwab@suse.de \
--cc=david.abdurachmanov@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
/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.