From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Kevin Tian" <kevin.tian@intel.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Jan Beulich" <JBeulich@suse.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Jun Nakajima" <jun.nakajima@intel.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 5/7] x86/vtx: Rename arch_vmx_struct to vmx_vcpu
Date: Wed, 29 Aug 2018 14:16:15 +0100 [thread overview]
Message-ID: <20180829131615.vimyuaw5issagdqt@citrix.com> (raw)
In-Reply-To: <83063641-99bf-4edc-2c59-6e4b24c2a5af@citrix.com>
On Wed, Aug 29, 2018 at 12:17:46PM +0100, Andrew Cooper wrote:
> On 29/08/18 09:03, Wei Liu wrote:
> > On Tue, Aug 28, 2018 at 06:39:04PM +0100, Andrew Cooper wrote:
> >> The suffix and prefix are redundant, and the name is curiously odd. Rename it
> >> to vmx_vcpu to be consistent with all the other similar structures.
> > What other similar structures do you have in mind?
>
> Most relevantly, {vmx,svm}_domain, but {pv,hvm}_{domain,vcpu} as well.
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-29 13:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 17:38 [PATCH 0/7] x86: Structure naming and consistency improvements Andrew Cooper
2018-08-28 17:39 ` [PATCH 1/7] x86/pv: Rename d->arch.pv_domain to d->arch.pv Andrew Cooper
2018-08-29 7:45 ` Wei Liu
2018-08-29 15:55 ` Jan Beulich
2018-08-28 17:39 ` [PATCH 2/7] x86/pv: Rename v->arch.pv_vcpu to v->arch.pv Andrew Cooper
2018-08-29 7:53 ` Wei Liu
2018-08-29 16:01 ` Jan Beulich
2018-08-28 17:39 ` [PATCH 3/7] xen/hvm: Rename d->arch.hvm_domain to d->arch.hvm Andrew Cooper
2018-08-28 18:56 ` Razvan Cojocaru
2018-08-29 7:56 ` Wei Liu
2018-08-30 1:34 ` Tian, Kevin
2018-08-30 14:39 ` Jan Beulich
2018-08-30 16:44 ` Julien Grall
2018-09-03 8:11 ` Paul Durrant
2018-08-28 17:39 ` [PATCH 4/7] x86/hvm: Rename v->arch.hvm_vcpu to v->arch.hvm Andrew Cooper
2018-08-28 18:59 ` Razvan Cojocaru
2018-08-29 7:57 ` Wei Liu
2018-08-30 1:34 ` Tian, Kevin
2018-08-30 14:52 ` Jan Beulich
2018-08-30 16:03 ` Andrew Cooper
2018-09-03 8:13 ` Paul Durrant
2018-08-28 17:39 ` [PATCH 5/7] x86/vtx: Rename arch_vmx_struct to vmx_vcpu Andrew Cooper
2018-08-29 8:03 ` Wei Liu
2018-08-29 11:17 ` Andrew Cooper
2018-08-29 13:16 ` Wei Liu [this message]
2018-08-30 1:36 ` Tian, Kevin
2018-08-30 14:54 ` Jan Beulich
2018-08-30 15:47 ` Andrew Cooper
2018-08-31 1:35 ` Tian, Kevin
2018-08-28 17:39 ` [PATCH 6/7] x86/svm: Rename arch_svm_struct to svm_vcpu Andrew Cooper
2018-08-30 14:54 ` Jan Beulich
2018-08-28 17:39 ` [PATCH 7/7] x86/hvm: Drop hvm_{vmx,svm} shorthands Andrew Cooper
2018-08-29 8:03 ` Wei Liu
2018-08-30 1:39 ` Tian, Kevin
2018-08-30 16:08 ` Andrew Cooper
2018-08-30 15:03 ` Jan Beulich
2018-08-30 23:11 ` Boris Ostrovsky
2018-08-30 23:14 ` Boris Ostrovsky
2018-08-30 23:18 ` Andrew Cooper
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=20180829131615.vimyuaw5issagdqt@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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 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).