From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] x86 emulator: Add 'push/pop sreg' instructions
Date: Wed, 19 Aug 2009 11:23:16 +0300 [thread overview]
Message-ID: <4A8BB674.8000401@redhat.com> (raw)
In-Reply-To: <52d4a3890908181240t2cfd696rf1b7a5d99175c0f7@mail.gmail.com>
On 08/18/2009 10:40 PM, Mohammed Gamal wrote:
>>
>>> + kvm_x86_ops->set_segment(ctxt->vcpu,&segment, seg);
>>>
>>>
> But we're popping the contents of the stack top to a segment register
> which is going to be of 16-bits anyway, so we know the length before
> hand, no?
>
No, the operand size attribute determines the change to rsp. If it's
larger than 2 bytes we drop the excess bits. See the documentation of
the POP instruction.
>> Note some of these instructions are not encodable in long mode; need to
>> check for that instead of emulating the wrong instruction.
>>
> I was under the impression that the emulator doesn't support long mode
> yet, is that still the case?
>
The emulator has always supported long mode, we need it for mmio and
pagetable updates.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-19 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 12:48 [PATCH] x86 emulator: Add 'push/pop sreg' instructions Mohammed Gamal
2009-08-18 14:39 ` Avi Kivity
2009-08-18 19:40 ` Mohammed Gamal
2009-08-19 8:23 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-19 4:11 Mohammed Gamal
2009-08-19 8:32 ` Avi Kivity
2009-08-19 12:52 ` Mohammed Gamal
2009-08-19 13:03 ` Avi Kivity
2009-08-19 13:26 Mohammed Gamal
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=4A8BB674.8000401@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.