From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v21 v2 1/2] x86/sgx: Use SRCU to protect mm_list during reclaim
Date: Fri, 12 Jul 2019 08:02:31 +0300 [thread overview]
Message-ID: <20190712050231.ramjbk25nqw7utz7@linux.intel.com> (raw)
In-Reply-To: <20190712034138.18564-2-sean.j.christopherson@intel.com>
On Thu, Jul 11, 2019 at 08:41:37PM -0700, Sean Christopherson wrote:
> + lockdep_assert_held_exclusive(&mm->mmap_sem);
Dropped for now as requires either LOCKDEP to Kconfig or #ifdef LOCKDEP
to the source.
/Jarkko
next prev parent reply other threads:[~2019-07-12 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 3:41 [PATCH for_v21 v2 0/2] x86/sgx: Use SRCU and mmu_notifier Sean Christopherson
2019-07-12 3:41 ` [PATCH for_v21 v2 1/2] x86/sgx: Use SRCU to protect mm_list during reclaim Sean Christopherson
2019-07-12 5:02 ` Jarkko Sakkinen [this message]
2019-07-12 3:41 ` [PATCH for_v21 v2 2/2] x86/sgx: Use mmu_notifier.release() instead of per-vma refcounting Sean Christopherson
2019-07-12 4:20 ` [PATCH for_v21 v2 0/2] x86/sgx: Use SRCU and mmu_notifier Jarkko Sakkinen
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=20190712050231.ramjbk25nqw7utz7@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@intel.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).