From: Chris Lalancette <clalance@redhat.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH]: Fix MSR_K7_EVNTSEL{0,3} for SVM
Date: Fri, 25 Apr 2008 09:06:56 -0400 [thread overview]
Message-ID: <4811D770.4090704@redhat.com> (raw)
In-Reply-To: <4811887E.6040202@qumranet.com>
Avi Kivity wrote:
>
> Hmm, looking back at the dump:
>
>> 1811: 8d 86 00 00 ff 3f lea 0x3fff0000(%rsi),%eax
>> 1817: 83 f8 03 cmp $0x3,%eax
>> 181a: 0f 87 e2 01 00 00 ja 1a02 <svm_set_msr+0x27f>
>
> So while gcc is using %rsi, it loads the result back into %eax, which
> has the effect of dropping back into 32-bits. So looks like gcc was
> right here. Sorry for spreading confusion and apologies to gcc.
>
OK. Well, then I can't explain why we are unconditionally calling
kvm_set_msr_common(), regardless of whether data == 0 or not. Avi, you said it
works for you; what version of gcc are you using, and can you send me your
objdump -Sr? I'd like to compare the assembly output with what 4.3.0 is
spitting out.
Chris Lalancette
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-25 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 18:23 [PATCH]: Fix MSR_K7_EVNTSEL{0,3} for SVM Chris Lalancette
2008-04-24 7:35 ` Avi Kivity
[not found] ` <4810926E.3070900@redhat.com>
2008-04-24 15:20 ` Avi Kivity
2008-04-24 15:44 ` Chris Lalancette
2008-04-24 22:13 ` Chris Lalancette
2008-04-25 7:30 ` Avi Kivity
2008-04-25 13:06 ` Chris Lalancette [this message]
2008-04-25 18:43 ` Chris Lalancette
2008-04-28 12:46 ` Joerg Roedel
2008-04-28 14:17 ` Chris Lalancette
2008-04-28 15:57 ` Joerg Roedel
2008-04-28 16:38 ` Chris Lalancette
2008-04-28 16:41 ` Andi Kleen
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=4811D770.4090704@redhat.com \
--to=clalance@redhat.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
/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.