From: Gleb Natapov <gleb@redhat.com>
To: alex <tomorrowanewday@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: patch for virtual machine oriented scheduling(3)
Date: Thu, 23 Apr 2009 14:39:39 +0300 [thread overview]
Message-ID: <20090423113939.GI24095@redhat.com> (raw)
In-Reply-To: <820ac2e90904230434m6df48866y26343e6435621748@mail.gmail.com>
On Thu, Apr 23, 2009 at 07:34:46PM +0800, alex wrote:
> On Thu, Apr 23, 2009 at 2:15 PM, Gleb Natapov <gleb@redhat.com> wrote:
> > On Wed, Apr 22, 2009 at 10:55:24PM +0800, alex wrote:
> >> the code for credit scheduler
> >> -----------------------------------------------------------------------------------------------------------------------
> >> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> >> index 4d76bb6..9e88ff0 100644
> >> --- a/arch/x86/kvm/lapic.c
> >> +++ b/arch/x86/kvm/lapic.c
> >> @@ -284,7 +284,7 @@ int kvm_apic_match_dest(struct kvm_vcpu *vcpu,
> >> struct kvm_lapic *source,
> >> "dest_mode 0x%x, short_hand 0x%x\n",
> >> target, source, dest, dest_mode, short_hand);
> >>
> >> - ASSERT(!target);
> >> + ASSERT(target);
> > Did you mean it?
>
> Yes.
Then send it as separate patch please.
> if target is not NULL, !target is 0, thus ASSERT(!target) will fail.
>
> from the context(and from the runtime output), it is easy to see that
> target should not be NULL.
>
> previously, this did not cause any problem is that DEBUG is not defined.
> If you define DEBUG the head of file lapic.c, and run KVM, you will
> find this bug.
--
Gleb.
next prev parent reply other threads:[~2009-04-23 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:55 patch for virtual machine oriented scheduling(3) alex
2009-04-23 6:15 ` Gleb Natapov
2009-04-23 11:34 ` alex
2009-04-23 11:39 ` Gleb Natapov [this message]
2009-04-23 11:39 ` alex
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=20090423113939.GI24095@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=tomorrowanewday@gmail.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