From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: keeping track of Intel vmcs
Date: Tue, 15 Mar 2011 19:58:15 -0700 [thread overview]
Message-ID: <20110315195815.17f9f0d1@mantra.us.oracle.com> (raw)
Hi,
I always wonder about intel vmcs info tracking when i have to look at
it. Following data structs are used to keep track of it:
static DEFINE_PER_CPU(struct foreign_vmcs, foreign_vmcs)
v->arch.hvm_vmx.active_cpu;
v->arch.hvm_vmx.launched;
v->arch.hvm_vmx.active_list;
static DEFINE_PER_CPU(struct vmcs_struct *, current_vmcs);
It appears to me that it could be lot simpler. All we need to worry about is
if a cpu needs to be launched or resumed. The rest can be concluded
from existing information. For example, current_vmcs and foreign_vmcs
seems redundant. If current == v, then we can conclude current_vmcs is
current, and forieng vmcs is not current! It seems all we need is
unsetting launched in vmpclear.
Can someone from Intel tell me what am I missing?
thanks
Mukesh
next reply other threads:[~2011-03-16 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 2:58 Mukesh Rathor [this message]
2011-03-16 8:11 ` keeping track of Intel vmcs Keir Fraser
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=20110315195815.17f9f0d1@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.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).