All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luke S. Crawford" <lsc@prgmr.com>
To: Jan Beulich <JBeulich@suse.com>, Sarah Newman <srn@prgmr.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handle
Date: Mon, 02 Dec 2013 01:58:16 -0800	[thread overview]
Message-ID: <529C59B8.6060201@prgmr.com> (raw)
In-Reply-To: <529C54170200007800108879@nat28.tlf.novell.com>

On 12/02/2013 12:34 AM, Jan Beulich wrote:
> The thing is that a guest admin may not have access to the VM's
> config file, i.e. a satisfactory solution ought to involve only guest
> side actions.

A service provider who allows customers to run their own kernel would 
see it the other way around.

That is the situation I find myself in.

I don't have access to my guest's config files.   Something I can do as 
the manager of the dom0 to ameliorate the problem without requiting the 
customers to do anything, and without requiring me to break into the 
guest and figure out how to patch whatever random kernel they might be 
using would help me a lot.

  reply	other threads:[~2013-12-02  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52967C45.3030506@prgmr.com>
2013-11-27 23:35 ` [PATCH] x86/fpu: CR0.TS should be set before trap into PV guest's #NM exception handle Sarah Newman
2013-11-29  9:42   ` Jan Beulich
2013-11-30  0:16     ` Sarah Newman
2013-12-02  8:34       ` Jan Beulich
2013-12-02  9:58         ` Luke S. Crawford [this message]
2013-12-02 10:04           ` Jan Beulich
2013-12-02 10:25             ` Luke S. Crawford

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=529C59B8.6060201@prgmr.com \
    --to=lsc@prgmr.com \
    --cc=JBeulich@suse.com \
    --cc=srn@prgmr.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 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.