This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] crash due to frequent access to csched_dom

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] crash due to frequent access to csched_dom
From: David Xu <davidxu06@xxxxxxxxx>
Date: Thu, 14 Jul 2011 14:42:11 -0400
Cc: George Dunlap <george.dunlap@xxxxxxxxxx>
Delivery-date: Thu, 14 Jul 2011 11:43:05 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NNP22vzt75iJ7wLnjcfjdFLjWnK9PefKHQN1Q6caJ78=; b=F2Cj+mR2Ozhoz/8/6kZYKUavVTdMgcpjAMRPLHfUoWbFNKjs/kiB64SKBxg+Rd136u 61d2qjZ0z1OfucPPspQJBV8OvFlIitfhR9Shc/1Me94NnnGzHM7C6hqIT3c9OaKLcN6y Hk4aBknulQIr7mvt2h7GgoqGTcXKTs6aDqsbE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAFLBxZb9WR8mEy7sKJji23mgtjGjbJAa2ktE7SVpe4TTRvndJg@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <CAGjowiTxUuTZ54F0r71N2XndqiN=SWcApxwKNOEh7vTWKtA_QQ@xxxxxxxxxxxxxx> <CAFLBxZb9WR8mEy7sKJji23mgtjGjbJAa2ktE7SVpe4TTRvndJg@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sorry, I do not have the serial port device now. It seems I can not access to csched_dom struct frequently during scheduling tick. For example, in each schedule tick, I will adjust the runqueue sequence according to the latency (another parameter added by myself) and remained credits of each domainU. This part code is added to the csched_vcpu_acct() or csched_runq_sort(). I also try accessing to sdom->weight, it also does not work. OK, I will try to set up a serial console firstly. Thanks very much.


2011/7/14 George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
On Wed, Jul 13, 2011 at 5:54 PM, David Xu <davidxu06@xxxxxxxxx> wrote:
> Hi,
> I am changing the credit1 scheduler. But I encountered a problem that the
> system will crash if I use some fileds  of struct csched_dom (e.t.
> sdom->weight, sdom->credit ) frequently in the csched_vcpu_acct() or
> csched_runq_sort(). It seems strange. Can anyone give me some suggestion or
> share your experience? Thanks.

Did you get any output on the serial console?

If you don't have a serial console set up, that's the first thing to
do.  It's immensely helpful when doing Xen debugging, especially
scheduler stuff.

You can learn more about setting up a Xen serial console here:



Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>