From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
paulus@samba.org, cyrilbur@gmail.com
Subject: Re: powerpc/tm: Avoid SLB faults in treclaim/trecheckpoint when RI=0
Date: Wed, 29 Jun 2016 16:43:03 +1000 (AEST) [thread overview]
Message-ID: <3rfY5g0yx8z9t0j@ozlabs.org> (raw)
In-Reply-To: <1467082864-7783-1-git-send-email-mikey@neuling.org>
On Tue, 2016-28-06 at 03:01:04 UTC, Michael Neuling wrote:
> Currently we have 2 segments that are bolted for the kernel linear
> mapping (ie 0xc000... addresses). This is 0 to 1TB and also the kernel
> stacks. Anything accessed outside of these regions may need to be
> faulted in.
...
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
> Reviewed-by: Cyril Bur <cyrilbur@gmail.com>
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/190ce8693c23eae09ba5f303a8
cheers
prev parent reply other threads:[~2016-06-29 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 3:01 [PATCH] powerpc/tm: Avoid SLB faults in treclaim/trecheckpoint when RI=0 Michael Neuling
2016-06-29 6:43 ` Michael Ellerman [this message]
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=3rfY5g0yx8z9t0j@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=paulus@samba.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).