From: Avi Kivity <avi@qumranet.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC 1/8]KVM: fix bugs in kvm sched integration patch
Date: Mon, 23 Jul 2007 13:46:43 +0300 [thread overview]
Message-ID: <46A48713.9080404@qumranet.com> (raw)
In-Reply-To: <1185173492.2645.65.camel@sli10-conroe.sh.intel.com>
Shaohua Li wrote:
> fix some bugs in kvm-sch patch.
>
There is now a 'preempt-hooks' branch on kvm.git with the preempt-hooks
work. I'll continually update and rebase it against master.
> 1. vmcs_readl/vmcs_writel are called with preempt enabled
>
Why is that bad?
> 2. preempt_count check doesn't make sense with preempt disabled
>
That is already fixed in the branch.
> 3. vmx_cpu_run doesn't handle error correctly and kvm_mmu_reload might
> sleep with mutex changes, so I move it above.
>
Yes.
> @@ -2001,6 +1997,10 @@ preempted:
> kvm_guest_debug_pre(vcpu);
>
> again:
> + r = kvm_mmu_reload(vcpu);
> + if (unlikely(r))
> + goto out;
> +
> preempt_disable();
>
> if (!vcpu->mmio_read_completed)
> @@ -2009,10 +2009,6 @@ again:
> vmx_save_host_state(vcpu);
> kvm_load_guest_fpu(vcpu);
>
> - r = kvm_mmu_reload(vcpu);
> - if (unlikely(r))
> - goto out;
> -
> /*
> * Loading guest fpu may have cleared host cr0.ts
> */
>
I'll add this (and the spinlock->mutex conversion) to the branch.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-07-23 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 6:51 [RFC 1/8]KVM: fix bugs in kvm sched integration patch Shaohua Li
2007-07-23 10:46 ` Avi Kivity [this message]
2007-07-24 1:45 ` Shaohua Li
2007-07-24 5:35 ` Avi Kivity
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=46A48713.9080404@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox