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] x86/sgx: rip off the refcount from sgx_encl_add_page flow
Date: Thu, 20 Jun 2019 22:23:40 +0300 [thread overview]
Message-ID: <20190620192340.GB15383@linux.intel.com> (raw)
In-Reply-To: <20190619154341.GF1203@linux.intel.com>
On Wed, Jun 19, 2019 at 08:43:41AM -0700, Sean Christopherson wrote:
> We should set SGX_ENCL_DEAD before flush_work(). Other than that I can't
> think of any issues with this approach. Though hopefully we can purge the
> worker altogether and make it a moot point :-).
Thanks, I squashed the change now. And definitely we can considere to
completely purge that. This change probably won't make it more
difficult :-)
I also removed PM notifier and SGX_ENCL_SUSPEND. Did not bother to cycle
that change here because on that we've already made conclusions. Just
have forgot to do that change.
/Jarkko
prev parent reply other threads:[~2019-06-20 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 12:21 [PATCH] x86/sgx: rip off the refcount from sgx_encl_add_page flow Jarkko Sakkinen
2019-06-19 15:43 ` Sean Christopherson
2019-06-20 19:23 ` Jarkko Sakkinen [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=20190620192340.GB15383@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).