From: Keir Fraser <keir@xen.org>
To: Christoph Egger <Christoph.Egger@amd.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] nestedsvm: ns_vmcb -> vvmcb
Date: Fri, 20 May 2011 08:57:34 +0100 [thread overview]
Message-ID: <C9FBDD7E.2D7D5%keir@xen.org> (raw)
In-Reply-To: <4DD393D9.70605@amd.com>
On 18/05/2011 10:39, "Christoph Egger" <Christoph.Egger@amd.com> wrote:
>
> Rename the virtual vmcb from ns_vmcb to vvmcb to
> make it easier for the reader what is meant.
I don't think vvmcb is a good idea. It's too close to vmcb. I think the
current name is actually okay, at least it is clearly distinct from anything
else. And you use the ns_ prefix quite consistently everywhere -- just
switching this one name would be weird.
-- Keir
> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
prev parent reply other threads:[~2011-05-20 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 9:39 [PATCH] nestedsvm: ns_vmcb -> vvmcb Christoph Egger
2011-05-20 7:57 ` Keir Fraser [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=C9FBDD7E.2D7D5%keir@xen.org \
--to=keir@xen.org \
--cc=Christoph.Egger@amd.com \
--cc=xen-devel@lists.xensource.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).