xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: "Hao, Xudong" <xudong.hao@intel.com>, Jan Beulich <JBeulich@suse.com>
Cc: Lars Kurth <lars.kurth@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.10.0 RC1 test result
Date: Thu, 2 Nov 2017 13:59:26 +0000	[thread overview]
Message-ID: <a180d55a-0854-99cf-9d51-a0d309626f2c@linaro.org> (raw)
In-Reply-To: <B8376D2DEA074F45BA033984477C453E3B83A44A@shsmsx102.ccr.corp.intel.com>

Hi,

On 30/10/17 02:21, Hao, Xudong wrote:
> 
>> -----Original Message-----
>> From: Jan Beulich [mailto:JBeulich@suse.com]
>> Sent: Friday, October 27, 2017 5:19 PM
>> To: Hao, Xudong <xudong.hao@intel.com>
>> Cc: Julien Grall <julien.grall@arm.com>; Lars Kurth <lars.kurth@citrix.com>;
>> xen-devel@lists.xen.org
>> Subject: Re: [Xen-devel] Xen 4.10.0 RC1 test result
>>
>>>>> On 27.10.17 at 10:28, <xudong.hao@intel.com> wrote:
>>> RAS:
>>> [BUG] xen-mceinj tool testing cause dom0 crash
>>> https://www.mail-archive.com/xen-devel@lists.xen.org/msg108671.html
>>
>> Please can you provide helpful links? This doesn't point to the beginning of the
>> thread, and the mail archive chosen doesn't appear to have an easy way to go
>> back to the head of a thread. And when I go through the parts of the thread
> 
> Unfortunately I didn't find the original link from mail-archive, but I pick up it in my mail client, attach the original mail.
> 
>> which are easily accessible there, it looks like you've never followed up on the
>> additional information (log) request.
> 
> I've provided the full log which included Xen and Dom0's, even though there was no valid error message from Dom0.
> 
>> This way I don't see how we can make
>> progress there.
> 
> Yes, this is the end mail https://www.mail-archive.com/xen-devel@lists.xen.org/msg108894.html.
> 
>> Plus, looking over the Cc lists there, Linux maintainers also don't
>> appear to have been involved at any time.
>>
> 
> I'm not sure if it's related with Dom0's kernel. My intention is we could discuss in Xen list only till we make sure it's Dom0's issue.

At the moment the discussion seem to be stuck on Xen list... Jan 
mentioned that for now he is not convinced it is a Xen bug. How about 
you CC Linux maintainers to get more feedback?

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-11-02 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  8:28 Xen 4.10.0 RC1 test result Hao, Xudong
2017-10-27  9:19 ` Jan Beulich
2017-10-30  2:21   ` Hao, Xudong
2017-11-02 13:59     ` Julien Grall [this message]
2017-11-03  8:42       ` Hao, Xudong
2017-11-06  8:24     ` Jan Beulich
2017-11-06  8:44       ` Hao, Xudong
2017-10-27  9:54 ` Andrew Cooper
2017-10-30  8:51   ` Hao, Xudong

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=a180d55a-0854-99cf-9d51-a0d309626f2c@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=JBeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xudong.hao@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;
as well as URLs for NNTP newsgroup(s).