From: Juergen Gross <jgross@suse.com>
To: "David Vrabel" <david.vrabel@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Kernel crash with "xen: avoid early crash of memory limited dom0"
Date: Fri, 4 Sep 2015 13:54:52 +0200 [thread overview]
Message-ID: <55E9868C.7090800@suse.com> (raw)
In-Reply-To: <55E96E2C.2090800@citrix.com>
On 09/04/2015 12:10 PM, David Vrabel wrote:
> On 04/09/15 10:48, Roger Pau Monné wrote:
>> Hello,
>>
>> The following commit:
>>
>> commit fa84f27e21200dbe7d18c21af424d1de703b7567
>> Author: Juergen Gross <jgross@suse.com>
>> Date: Wed Aug 19 18:52:34 2015 +0200
>>
>> xen: avoid early crash of memory limited dom0
>>
>> Which is queued in:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.3
>
> I was going to send the pull request for this branch today but I guess
> it'll have to wait until next week.
>
> Juergen, if a fix for this isn't available by Wednesday next week I'll
> shall have to drop all the >512 GB support patches from this branch.
I've been able to reproduce the issue and found the problem
already. David, do you want an incremental patch or V2 of the
problematic patch Roger mentioned (it's just one line)?
Roger, I think I don't need your kernel config any longer. The
relevant information was to be found in the register context. :-)
Juergen
next prev parent reply other threads:[~2015-09-04 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 9:48 Kernel crash with "xen: avoid early crash of memory limited dom0" Roger Pau Monné
2015-09-04 10:08 ` Juergen Gross
2015-09-04 10:10 ` [Xen-devel] " David Vrabel
2015-09-04 11:54 ` Juergen Gross [this message]
2015-09-04 12:03 ` David Vrabel
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=55E9868C.7090800@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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