From: Leonardo Bras <leonardo@linux.ibm.com>
To: jhubbard@nvidia.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
linux-arch@vger.kernel.org, linux-mm@kvack.org
Cc: keith.busch@intel.com, tglx@linutronix.de, arnd@arndb.de,
gregkh@linuxfoundation.org, yuehaibing@huawei.com,
npiggin@gmail.com, rppt@linux.ibm.com, mahesh@linux.vnet.ibm.com,
jgg@ziepe.ca, paulus@samba.org, aneesh.kumar@linux.ibm.com,
ganeshgr@linux.ibm.com, akpm@linux-foundation.org,
ira.weiny@intel.com, dan.j.williams@intel.com,
allison@lohutok.net
Subject: Re: [PATCH v3 00/11] Introduces new count-based method for monitoring lockless pagetable walks
Date: Fri, 27 Sep 2019 20:25:15 -0300 [thread overview]
Message-ID: <ed1a954a67de3b1fa66e921883153622f3446813.camel@linux.ibm.com> (raw)
In-Reply-To: <8fe1ee1abf52719e75902dc7d5cd1e91751eaba7.camel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
On Fri, 2019-09-27 at 11:46 -0300, Leonardo Bras wrote:
> I am not sure if it would be ok to use irq_{save,restore} in real mode,
> I will do some more reading of the docs before addressing this.
It looks like it's unsafe to merge irq_{save,restore} in
{start,end}_lockless_pgtbl_walk(), due to a possible access of code
that is not accessible in real mode.
I am sending a v4 for the changes so far.
I will look forward for your feedback.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-27 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 14:46 [PATCH v3 00/11] Introduces new count-based method for monitoring lockless pagetable walks Leonardo Bras
2019-09-27 23:25 ` Leonardo Bras [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-24 21:24 Leonardo Bras
2019-09-24 22:58 ` John Hubbard
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=ed1a954a67de3b1fa66e921883153622f3446813.camel@linux.ibm.com \
--to=leonardo@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=allison@lohutok.net \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=ganeshgr@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=keith.busch@intel.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=rppt@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=yuehaibing@huawei.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 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).