From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Kurt Yoder <ktykvm@yoderhome.com>, kvm@vger.kernel.org
Subject: Re: IO on guest is 20 times slower than host
Date: Tue, 31 Mar 2009 13:02:44 +0300 [thread overview]
Message-ID: <49D1EA44.1090406@redhat.com> (raw)
In-Reply-To: <20090331095956.GB21083@amd.com>
Joerg Roedel wrote:
>> --- a/kernel/x86/kvm/svm.c
>> +++ b/kernel/x86/kvm/svm.c
>> @@ -575,7 +575,7 @@ static void init_vmcb(struct vcpu_svm *svm)
>> INTERCEPT_CR3_MASK);
>> control->intercept_cr_write &= ~(INTERCEPT_CR0_MASK|
>> INTERCEPT_CR3_MASK);
>> - save->g_pat = 0x0007040600070406ULL;
>> + save->g_pat = 0x0606060606060606ULL;
>> /* enable caching because the QEMU Bios doesn't enable it */
>> save->cr0 = X86_CR0_ET;
>> save->cr3 = 0;
>>
>
> Yeah, that patch makes sense. But I think we need some more work on this
> because the guest may change the pat msr afterwards. Best would be a simple
> shadow of the pat msr. Last question is how this will effect pci passthrough.
This is just a stopgap; we can later add proper pat shadowing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-31 10:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 15:23 IO on guest is 20 times slower than host Kurt Yoder
2009-03-25 16:13 ` Avi Kivity
2009-03-25 16:28 ` Kurt Yoder
2009-03-25 16:35 ` Avi Kivity
2009-03-25 16:51 ` Kurt Yoder
2009-03-25 16:54 ` Avi Kivity
2009-03-25 17:11 ` Kurt Yoder
2009-03-25 17:55 ` Avi Kivity
2009-03-25 18:51 ` Kurt Yoder
2009-03-26 10:16 ` Avi Kivity
2009-03-27 13:53 ` Kurt Yoder
2009-03-27 14:03 ` Kurt Yoder
2009-03-27 14:10 ` Kurt Yoder
2009-03-29 14:29 ` Avi Kivity
2009-03-29 19:10 ` Avi Kivity
2009-03-31 9:59 ` Joerg Roedel
2009-03-31 10:02 ` Avi Kivity [this message]
2009-04-04 11:47 ` Avi Kivity
2009-03-30 19:39 ` Kurt Yoder
2009-03-31 15:15 ` Kurt Yoder
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=49D1EA44.1090406@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=ktykvm@yoderhome.com \
--cc=kvm@vger.kernel.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