From: Mohammed Gamal <m.gamal005@gmail.com>
To: avi@redhat.com
Cc: mtosatti@redhat.com, kvm@vger.kernel.org,
Mohammed Gamal <m.gamal005@gmail.com>
Subject: [RFC PATCH v2 2/3] x86 emulator: Add cs_base() helper
Date: Thu, 8 Jul 2010 17:10:35 +0300 [thread overview]
Message-ID: <1278598236-12103-3-git-send-email-m.gamal005@gmail.com> (raw)
In-Reply-To: <1278598236-12103-1-git-send-email-m.gamal005@gmail.com>
Adds a cs_base() helper for consistency with other emulator functions
Signed-off-by: Mohammed Gamal <m.gamal005@gmail.com>
---
arch/x86/kvm/emulate.c | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index 255473f..6bb7c68 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/kvm/emulate.c
@@ -643,6 +643,12 @@ static unsigned long seg_override_base(struct x86_emulate_ctxt *ctxt,
return seg_base(ctxt, ops, c->seg_override);
}
+static unsigned long cs_base(struct x86_emulate_ctxt *ctxt,
+ struct x86_emulate_ops *ops)
+{
+ return seg_base(ctxt, ops, VCPU_SREG_CS);
+}
+
static unsigned long es_base(struct x86_emulate_ctxt *ctxt,
struct x86_emulate_ops *ops)
{
@@ -976,7 +982,7 @@ x86_decode_insn(struct x86_emulate_ctxt *ctxt, struct x86_emulate_ops *ops)
c->eip = ctxt->eip;
c->fetch.start = c->fetch.end = c->eip;
- ctxt->cs_base = seg_base(ctxt, ops, VCPU_SREG_CS);
+ ctxt->cs_base = cs_base(ctxt, ops);
switch (mode) {
case X86EMUL_MODE_REAL:
--
1.7.0.4
next prev parent reply other threads:[~2010-07-08 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 14:10 [RFC PATCH v2 0/3] Add segment limit checks to emulator Mohammed Gamal
2010-07-08 14:10 ` [RFC PATCH v2 1/3] Add helper methods to get segment limits Mohammed Gamal
2010-07-08 14:10 ` Mohammed Gamal [this message]
2010-07-08 14:10 ` [RFC PATCH v2 3/3] x86 emulator: Add segment limit checks and helper functions Mohammed Gamal
2010-07-11 18:07 ` Avi Kivity
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=1278598236-12103-3-git-send-email-m.gamal005@gmail.com \
--to=m.gamal005@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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).