From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Yang, Sheng" <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Enable memory mapped TPR shadow(FlexPriority)
Date: Wed, 24 Oct 2007 12:15:38 +0200 [thread overview]
Message-ID: <471F1B4A.8070600@qumranet.com> (raw)
In-Reply-To: <DB3BD37E3533EE46BED2FBA80995557F9BE831-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Yang, Sheng wrote:
> Avi Kivity wrote:
>
>> Yang, Sheng wrote:
>>
>>> Another comment: I forgot if I answer the question on why eip should
>>>
> move
>
>>> backward. I did it because some instruction like "mov" will move eip
>>>
> to
>
>>> skip some dst/src operand when executing, so eip should be kept for
>>> consistency.
>>>
>>>
>> I think you're talking about
>>
>>
>>> case 0xa0 ... 0xa1: /* mov */
>>> c->dst.ptr = (unsigned long *)&c->regs[VCPU_REGS_RAX];
>>> c->dst.val = c->src.val;
>>> /* skip src displacement */
>>> c->eip += c->ad_bytes;
>>> break;
>>>
>> ?
>>
>> If so, instead of skipping, we can fetch the address here.
>>
>> It's been annoying me for a long time; it causes a dependency on cr2
>> which we don't have in real mode (and with FlexPriority), and which is
>> broken anyway because cr2 points at the wrong address during a page
>> fault on the second page of a misaligned cross-page access.
>>
>
> Yeah, like that. But I don't think only "mov" has memory operand, so
> fetch
> address in some determined place is better than inside every instruction
> executing
> code.
>
>
I think mov is the only instruction that uses absolute addresses without
modrm encoding. And modrm encoding is implemented correctly for a long
time.
> Another thing, if we can use physical address as supplement of cr2 in
> emulate_instrcutions,
> that will be better. Any suggestion?
>
Sorry, I don't understand the question.
I'd like to see cr2 completely removed from x86_emulate.c.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-24 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 3:01 [PATCH] Enable memory mapped TPR shadow(FlexPriority) Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE64A-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-24 9:13 ` Avi Kivity
[not found] ` <471F0CCA.7060108-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-24 10:02 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE831-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-24 10:15 ` Avi Kivity [this message]
[not found] ` <471F1B4A.8070600-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-24 10:18 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE834-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-24 10:19 ` Avi Kivity
[not found] ` <471F1C49.4010609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-24 13:08 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE84F-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-24 13:16 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2007-10-24 2:55 Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE63D-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-24 9:10 ` Avi Kivity
[not found] ` <471F0BF2.3040901-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-24 10:02 ` Yang, Sheng
[not found] ` <DB3BD37E3533EE46BED2FBA80995557F9BE830-wq7ZOvIWXbM/UvCtAeCM4rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-25 18:55 ` Avi Kivity
2007-10-24 12:48 ` Izik Eidus
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=471F1B4A.8070600@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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