From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: David Daney <ddaney.cavm@gmail.com>, <linux-mips@linux-mips.org>,
<ralf@linux-mips.org>, David Daney <david.daney@cavium.com>,
<stable@vger.kernel.org>
Subject: Re: MIPS: Make set_pte() SMP safe.
Date: Tue, 4 Aug 2015 13:47:10 -0700 [thread overview]
Message-ID: <55C124CE.3070209@imgtec.com> (raw)
In-Reply-To: <55C122D7.3040803@caviumnetworks.com>
On 08/04/2015 01:38 PM, David Daney wrote:
> I don't know what the purpose of guard pages is. I thought it was to
> produce an OOPs message if you accessed just beyond the end of the
> vmap area. If people are using them for some other reason, then I am
> not aware of it.
>
>
Right, but if you have a buddy problem then it means that in your case
the guard page IS USED... and doesn't produce OOPs.
WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
linux-mips@linux-mips.org, ralf@linux-mips.org,
David Daney <david.daney@cavium.com>,
stable@vger.kernel.org
Subject: Re: MIPS: Make set_pte() SMP safe.
Date: Tue, 4 Aug 2015 13:47:10 -0700 [thread overview]
Message-ID: <55C124CE.3070209@imgtec.com> (raw)
Message-ID: <20150804204710.4pnB6WClGVMxapuhYPN19I1v6A-yXc4Cxs0AKPrlaBY@z> (raw)
In-Reply-To: <55C122D7.3040803@caviumnetworks.com>
On 08/04/2015 01:38 PM, David Daney wrote:
> I don't know what the purpose of guard pages is. I thought it was to
> produce an OOPs message if you accessed just beyond the end of the
> vmap area. If people are using them for some other reason, then I am
> not aware of it.
>
>
Right, but if you have a buddy problem then it means that in your case
the guard page IS USED... and doesn't produce OOPs.
next prev parent reply other threads:[~2015-08-04 20:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 0:48 [PATCH] MIPS: Make set_pte() SMP safe David Daney
2015-08-04 0:48 ` David Daney
2015-08-04 19:15 ` Leonid Yegoshin
2015-08-04 19:15 ` Leonid Yegoshin
2015-08-04 20:01 ` David Daney
2015-08-04 20:01 ` David Daney
2015-08-04 20:32 ` Leonid Yegoshin
2015-08-04 20:32 ` Leonid Yegoshin
2015-08-04 20:36 ` Leonid Yegoshin
2015-08-04 20:36 ` Leonid Yegoshin
2015-08-04 20:38 ` David Daney
2015-08-04 20:38 ` David Daney
2015-08-04 20:47 ` Leonid Yegoshin [this message]
2015-08-04 20:47 ` Leonid Yegoshin
2015-08-04 20:48 ` David Daney
2015-08-04 20:48 ` David Daney
2015-08-04 20:58 ` Leonid Yegoshin
2015-08-04 20:58 ` Leonid Yegoshin
2015-08-24 3:28 ` [PATCH] " Joshua Kinard
-- strict thread matches above, loose matches on Subject: below --
2015-08-04 0:48 David Daney
2015-08-04 0:48 David Daney
2015-08-04 0:48 David Daney
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=55C124CE.3070209@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--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.