xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir@xen.org>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86-64: refine the XSA-9 fix
Date: Fri, 17 Aug 2012 17:11:36 +0200	[thread overview]
Message-ID: <20120817151136.GA25138@aepfle.de> (raw)
In-Reply-To: <CC04F47B.431CE%keir@xen.org>

On Mon, Jun 18, Keir Fraser wrote:

> On 13/06/2012 11:04, "Jan Beulich" <JBeulich@suse.com> wrote:
> 
> > Our product management wasn't happy with the "solution" for XSA-9, and
> > demanded that customer systems must continue to boot. Rather than
> > having our and perhaps other distros carry non-trivial patches, allow
> > for more fine grained control (panic on boot, deny guest creation, or
> > merely warn) by means of a single line change.
> 
> All this seems to allow is to boot but not create domU-s. Which seems a bit
> pointless.

Refusing to boot into dom0 with no good reason is a good way to lose
remote control of a system without serial console. Not funny.

Fortunately I booted and tested with sles11 Xen first before ruining the
box with plain xen-unstable.

So, please apply this patch and remove the panic() from ./xen/arch/x86/cpu/amd.c

Olaf

  parent reply	other threads:[~2012-08-17 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 10:04 [PATCH] x86-64: refine the XSA-9 fix Jan Beulich
2012-06-18 14:06 ` Keir Fraser
2012-06-18 14:28   ` Jan Beulich
2012-08-17 15:11   ` Olaf Hering [this message]
2012-08-17 15:48     ` Keir Fraser
2012-08-17 15:56       ` Olaf Hering
2012-08-17 16:28         ` Jan Beulich
2012-08-17 16:41           ` Keir Fraser
2012-08-17 15:49 ` Keir Fraser

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=20120817151136.GA25138@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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 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).