From: Will Deacon <will@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
stable <stable@vger.kernel.org>,
Alistair Delva <adelva@google.com>,
Sandeep Patil <sspatil@google.com>
Subject: Re: [PATCH] arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default
Date: Tue, 5 Nov 2019 18:22:29 +0000 [thread overview]
Message-ID: <20191105182228.GA388@willie-the-truck> (raw)
In-Reply-To: <CALAqxLVT-SK0-nNUmbDWa3kkZED2z+pcryzuue9c=n42shu3kA@mail.gmail.com>
On Tue, Nov 05, 2019 at 09:06:43AM -0800, John Stultz wrote:
> On Tue, Nov 5, 2019 at 2:29 AM Will Deacon <will@kernel.org> wrote:
> > On Mon, Nov 04, 2019 at 05:16:42PM -0800, John Stultz wrote:
> > > So I'm not yet sure why, but I've just validated that this patch is
> > > causing trouble with booting AOSP on HiKey960 with 5.4-rc6 (-rc5 works
> > > fine).
[...]
> > As an experiment, can you try reverting just the part of the patch that
> > removes PTE_DIRTY from the PROT_* definitions? (see below)
>
> I'll give this a try! Feel free to let me know if there's anything
> else I should test.
Thanks. Also worth trying to revert 747a70e60b72 instead of this patch, as
Catalin suggested.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Alistair Delva <adelva@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Sandeep Patil <sspatil@google.com>,
stable <stable@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default
Date: Tue, 5 Nov 2019 18:22:29 +0000 [thread overview]
Message-ID: <20191105182228.GA388@willie-the-truck> (raw)
In-Reply-To: <CALAqxLVT-SK0-nNUmbDWa3kkZED2z+pcryzuue9c=n42shu3kA@mail.gmail.com>
On Tue, Nov 05, 2019 at 09:06:43AM -0800, John Stultz wrote:
> On Tue, Nov 5, 2019 at 2:29 AM Will Deacon <will@kernel.org> wrote:
> > On Mon, Nov 04, 2019 at 05:16:42PM -0800, John Stultz wrote:
> > > So I'm not yet sure why, but I've just validated that this patch is
> > > causing trouble with booting AOSP on HiKey960 with 5.4-rc6 (-rc5 works
> > > fine).
[...]
> > As an experiment, can you try reverting just the part of the patch that
> > removes PTE_DIRTY from the PROT_* definitions? (see below)
>
> I'll give this a try! Feel free to let me know if there's anything
> else I should test.
Thanks. Also worth trying to revert 747a70e60b72 instead of this patch, as
Catalin suggested.
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-05 18:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 15:30 [PATCH] arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default Catalin Marinas
2019-10-29 15:30 ` Catalin Marinas
2019-10-29 16:52 ` Will Deacon
2019-10-29 16:52 ` Will Deacon
2019-11-05 1:16 ` John Stultz
2019-11-05 1:16 ` John Stultz
2019-11-05 10:29 ` Will Deacon
2019-11-05 10:29 ` Will Deacon
2019-11-05 16:54 ` Catalin Marinas
2019-11-05 16:54 ` Catalin Marinas
2019-11-05 21:17 ` John Stultz
2019-11-05 21:17 ` John Stultz
2019-11-05 21:29 ` John Stultz
2019-11-05 21:29 ` John Stultz
2019-11-06 8:59 ` Catalin Marinas
2019-11-06 8:59 ` Catalin Marinas
2019-11-05 17:06 ` John Stultz
2019-11-05 17:06 ` John Stultz
2019-11-05 18:22 ` Will Deacon [this message]
2019-11-05 18:22 ` Will Deacon
2019-11-06 4:56 ` John Stultz
2019-11-06 4:56 ` John Stultz
2019-11-05 21:24 ` John Stultz
2019-11-05 21:24 ` John Stultz
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=20191105182228.GA388@willie-the-truck \
--to=will@kernel.org \
--cc=adelva@google.com \
--cc=catalin.marinas@arm.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sspatil@google.com \
--cc=stable@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.