From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] CC_DST problem
Date: Wed, 29 Aug 2007 22:58:00 +0200 [thread overview]
Message-ID: <46D5DDD8.3080804@bellard.org> (raw)
In-Reply-To: <46D59E6B.1000606@suse.de>
Alexander Graf wrote:
> Hi,
>
> I'm still trying to implement SVM correctly and hit a serious problem.
> If I set CC_OP to EFLAGS / DYNAMIC after each instruction (so most
> conditional operations are based on EFLAGS) everything works as expected.
> If using CC_OP==CC_OP_EFLAGS only CC_SRC should be used and CC_DST is
> supposed to be completely ignored.
>
> So I set CC_DST to 0 (this happens when leaving and rejoining the
> virtual machine, so this is the real problem) and if I do that, I get
> funny segmentation faults in x86_64 guest userspace programs running in
> the virtual machine (this is exactly what I see in kvm with my current
> patchset as well), while 32 bit userspace programs simply hang.
> So I guess this is the real problem.
>
> Is there any logical reason CC_DST could be used with CC_OP==CC_OP_EFLAGS?
>
> Attached to this email you will find a small patch that triggers this
> problem.
>
> Thanks for any reply that could help on this,
>
> Alexander Graf
If you play with the CC_OP logic, it is better to disable the eflags
optimization code in the translator (optimize_flags() function).
Regarding the implementation for SVM, you can look at how the CC are
handled in SMM (do_smm_enter and helper_rsm). I see no particular
problem here.
I suggest to try to suppress the additions in the static translator
state as I feel most of the SVM intercepts can be tested in helpers
where speed is not critical.
Regards,
Fabrice.
prev parent reply other threads:[~2007-08-29 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:27 [Qemu-devel] CC_DST problem Alexander Graf
2007-08-29 20:58 ` Fabrice Bellard [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=46D5DDD8.3080804@bellard.org \
--to=fabrice@bellard.org \
--cc=qemu-devel@nongnu.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 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.