public inbox for linux-sgx@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhiquan Li <zhiquan1.li@intel.com>
To: "Huang, Kai" <kai.huang@intel.com>,
	"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Cc: "Du, Fan" <fan.du@intel.com>, "Christopherson,,
	Sean" <seanjc@google.com>, "Zhang, Cathy" <cathy.zhang@intel.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"bp@alien8.de" <bp@alien8.de>
Subject: Re: [PATCH v7 1/3] x86/sgx: Rename the owner field of struct sgx_epc_page as encl_owner
Date: Thu, 1 Sep 2022 17:30:58 +0800	[thread overview]
Message-ID: <bcbc1b4c-3db4-c9c8-01f3-d89849b40ff5@intel.com> (raw)
In-Reply-To: <7d222818eabcecc1376c616f8f2fcbb89f0df70e.camel@intel.com>


On 2022/9/1 11:36, Huang, Kai wrote:
> On Thu, 2022-09-01 at 08:35 +0800, Zhiquan Li wrote:
>> In order to avoid unnecessary casting, rename the 'owner' field of
>> struct sgx_epc_page as 'encl_owner', and update all of references.
> This changelog itself doesn't explain _why_ renaming 'owner' to 'encl_owner' can
> avoid the explicit casting.  In fact, the reason is that you will use a 'union'
> to separate the use of 'owner' of the EPC page (between SGX driver and virtual
> EPC).  The rename is just to make the name more clear, but cannot really avoid
> casting.
> 
> So I think there should be more sentences to explain here, such as "in order to
> send SIGBUS to userspace hypervisor to allow it to inject #MC to guest, use
> virtual EPC page's owner to be the userspace virtual address of the EPC page",
> and after those you can say something like "in order to avoid casting, use a
> union to separate the use of owner for SGX driver EPC page and virtual EPC page.
> And rename owner of SGX driver EPC page to 'encl_owner' to be more specific",
> etc.
> 
> That being said, I guess you can just merge this patch with your second patch,
> which actually introduces the 'union' and uses the owner for virtual EPC page.
> And in changelog you explain everything above to justify the patch.
> 
> Does this make sense?

Thanks for your review and sentences, Kai!

Hi Jarkko,

Do you agree Kai's proposal? That is, merging patch 01 (just rename, no
functional changes) and patch 02 (introduce a union and utilize the
'vepc_vaddr' field) into one.

- If yes, I'll do it like Kai said.
- If not, I'll just enrich the commit message of patch 01 and keep it
separately.

Best Regards,
Zhiquan

> 
>> Signed-off-by: Zhiquan Li <zhiquan1.li@intel.com>
>>
>> ---
>> Changes since V6:
>> - Revise the commit message suggested by Jarkko.
>>   Link: https://lore.kernel.org/linux-sgx/20220826160503.1576966-1-zhiquan1.li@intel.com/T/#mb201506ed06932438c82d48915cd4ceae9745bc2
>> ---

  reply	other threads:[~2022-09-01  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01  0:35 [PATCH v7 0/3] x86/sgx: fine grained SGX MCA behavior Zhiquan Li
2022-09-01  0:35 ` [PATCH v7 1/3] x86/sgx: Rename the owner field of struct sgx_epc_page as encl_owner Zhiquan Li
2022-09-01  3:36   ` Huang, Kai
2022-09-01  9:30     ` Zhiquan Li [this message]
2022-09-09 12:50     ` Zhiquan Li
2022-09-12 10:01       ` Huang, Kai
2022-09-01  0:36 ` [PATCH v7 2/3] x86/sgx: Introduce union with vepc_vaddr field for virtualization case Zhiquan Li
2022-09-01  0:36 ` [PATCH v7 3/3] x86/sgx: Fine grained SGX MCA behavior for virtualization Zhiquan Li
2022-09-01 22:29 ` [PATCH v7 0/3] x86/sgx: fine grained SGX MCA behavior 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=bcbc1b4c-3db4-c9c8-01f3-d89849b40ff5@intel.com \
    --to=zhiquan1.li@intel.com \
    --cc=bp@alien8.de \
    --cc=cathy.zhang@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=fan.du@intel.com \
    --cc=jarkko@kernel.org \
    --cc=kai.huang@intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@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