From: "Wei, Gang" <gang.wei@intel.com>
To: Keir Fraser <keir@xen.org>,
"Zheng, Shaohui" <shaohui.zheng@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: "Wei, Gang" <gang.wei@intel.com>
Subject: RE: RE: Xen 4.1 rc1 test report
Date: Tue, 25 Jan 2011 23:49:36 +0800 [thread overview]
Message-ID: <F26D193E20BBDC42A43B611D1BDEDE7125563786AB@shsmsx502.ccr.corp.intel.com> (raw)
In-Reply-To: <C9648AEF.1265C%keir@xen.org>
Keir Fraser wrote on 2011-01-25:
> On 25/01/2011 14:05, "Wei, Gang" <gang.wei@intel.com> wrote:
>
>> 3. Think about how we could prevent such cases from panic Xen.
>>
>> Any ideas, hints, comments, suggestions or even fixes on it?
>
> Either the domain destroy path should forcibly unbind pirqs, or a
> non-empty set of pirq bindings should hold at least one reference to a
> domain, to prevent it being destroyed+freed.
>
> Is forcible unbinding ever dangerous to system stability? If not
> perhaps that is best.
I agree, and will have a try in this way.
Jimmy
next prev parent reply other threads:[~2011-01-25 15:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 16:37 Xen 4.1 rc1 test report Zheng, Shaohui
2011-01-22 16:54 ` Mike Viau
2011-01-23 2:34 ` Zheng, Shaohui
2011-01-24 19:00 ` Stefano Stabellini
2011-01-25 3:42 ` Zhang, Yang Z
2011-01-25 11:23 ` Stefano Stabellini
2011-01-25 16:01 ` Stefano Stabellini
2011-01-26 1:01 ` Zheng, Shaohui
2011-01-26 3:54 ` Zheng, Shaohui
2011-01-26 4:53 ` Zheng, Shaohui
2011-01-25 10:10 ` Pasi Kärkkäinen
2011-01-25 15:49 ` Stefano Stabellini
2011-01-26 3:56 ` Zheng, Shaohui
2011-01-25 14:05 ` Wei, Gang
2011-01-25 14:13 ` Keir Fraser
2011-01-25 15:49 ` Wei, Gang [this message]
2011-01-26 5:52 ` Wei, Gang
2011-01-26 6:31 ` Wei, Gang
2011-01-26 7:24 ` Keir Fraser
2011-01-26 7:34 ` Wei, Gang
2011-01-26 14:38 ` Wei, Gang
2011-01-26 7:28 ` [PATCH] Fix bug1706 Wei, Gang
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=F26D193E20BBDC42A43B611D1BDEDE7125563786AB@shsmsx502.ccr.corp.intel.com \
--to=gang.wei@intel.com \
--cc=keir@xen.org \
--cc=shaohui.zheng@intel.com \
--cc=xen-devel@lists.xensource.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 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.