From: Martin Wilck <mwilck@arcor.de>
To: "Wang, Winston L" <winston.l.wang@intel.com>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
KeirFraser <keir@xen.org>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
"Dugger, Donald D" <donald.d.dugger@intel.com>,
Jan Beulich <JBeulich@novell.com>, "Li, Xin" <xin.li@intel.com>
Subject: Re: Re: system freeze when processor.ko is loaded
Date: Sun, 17 Apr 2011 21:38:59 +0200 [thread overview]
Message-ID: <4DAB41D3.3080708@arcor.de> (raw)
In-Reply-To: <54B2EB610B7F1340BB6A0D4CA04A4F100100C0A0A2@orsmsx505.amr.corp.intel.com>
Hi,
> Sounds good, I don't have the failed the processors
> Martin, does Jan's patch fix the problem of your failed platform?
Yes, Jan's patch (on top of the OpenSUSE Xen release) worked well for me.
>> clearly secondary (and honestly I don't think anyone wants to waste
>> cycles on improving this for the few old processors that are still out
>> there and that Xen is being run on).
> Agree.
As you may imagine, I am not too happy about that, but I understand that
the lead Xen developers have different priorities.
Martin
prev parent reply other threads:[~2011-04-17 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d6cfc1ce-e4b3-47dc-ae83-8d0c341988b3@rrsmsx606.amr.corp.intel.com>
2011-04-11 22:35 ` Re: system freeze when processor.ko is loaded Wang, Winston L
2011-04-12 7:03 ` Jan Beulich
2011-04-12 17:27 ` Wang, Winston L
2011-04-12 17:32 ` Keir Fraser
2011-04-13 6:50 ` Jan Beulich
2011-04-13 18:06 ` Wang, Winston L
2011-04-17 19:38 ` Martin Wilck [this message]
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=4DAB41D3.3080708@arcor.de \
--to=mwilck@arcor.de \
--cc=JBeulich@novell.com \
--cc=donald.d.dugger@intel.com \
--cc=jinsong.liu@intel.com \
--cc=keir@xen.org \
--cc=winston.l.wang@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.li@intel.com \
--cc=yunhong.jiang@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 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.