All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Xen-devel List <xen-devel@lists.xen.org>
Subject: Re: Backport suggestions for Xen 4.4
Date: Tue, 24 Jun 2014 11:53:06 +0100	[thread overview]
Message-ID: <53A95892.7020901@citrix.com> (raw)
In-Reply-To: <53A9714D020000780001CBBD@mail.emea.novell.com>

On 24/06/14 11:38, Jan Beulich wrote:
>>>> On 24.06.14 at 12:23, <andrew.cooper3@citrix.com> wrote:
>> Some further backport suggestions, from the XenServer patch queue.
> Thanks.
>
>> Xen bugfixes:
>> * 415738e "x86/traps: make panic and reboot paths safe during early boot"
>> * d4f88fc "make the main trap handlers safe for use early during Xen boot"
> Honestly I'd rather stay away from backporting these, no matter that
> I'm convinced they're working fine.

There are pre-existing cases where it is possible to crash and attempt
to reboot before sufficiently setting up state for machine_reboot() to
be safe.  In other words, 415738e is genuine bugfix for a real customer
escalation.

>
>> ** including "\n" fix for #MC handler from b30d333
> Purely cosmetic - we're about to die anyway when this message
> gets printed, so it not being printed on its own line is the smallest
> of our problems.
>
>> * 92009d3 "x86/boot: correct CR4 setup on APs"
> This might be acceptable, but would need validation that it really
> addresses in the stable trees what it does in -unstable without the
> other early trap handling changes. The one comment it adds to
> start_secondary() suggests that this might not be the case.

The cr4 problems were completely independent from the early trap
problems, on further consideration this is not quite correct on its own
without the other early trap series (which has been backported into
XenServer)

I can do a backport to 4.4 which resolves the interaction issue with the
early trap series, if that would help.

~Andrew

  reply	other threads:[~2014-06-24 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 10:23 Backport suggestions for Xen 4.4 Andrew Cooper
2014-06-24 10:38 ` Jan Beulich
2014-06-24 10:53   ` Andrew Cooper [this message]
2014-06-24 11:57     ` Jan Beulich

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=53A95892.7020901@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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 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.