From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefan Bader <stefan.bader@canonical.com>,
Matt Wilson <msw@amazon.com>,
"Justin M. Forbes" <jmforbes@linuxtx.org>,
xen-devel@lists.xen.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH/RFC] Fix xsave bug on older Xen hypervisors
Date: Fri, 7 Sep 2012 11:48:27 -0400 [thread overview]
Message-ID: <20120907154827.GA6059@phenom.dumpdata.com> (raw)
In-Reply-To: <504A347B0200007800099E92@nat28.tlf.novell.com>
On Fri, Sep 07, 2012 at 04:52:59PM +0100, Jan Beulich wrote:
> >>> On 07.09.12 at 17:47, Stefan Bader <stefan.bader@canonical.com> wrote:
> > On 07.09.2012 17:44, Jan Beulich wrote:
> >> All of this still doesn't provide evidence that a plain upstream
> >> kernel is actually having any problems in the first place. Further,
> >> if you say EC2 has a crippled hypervisor patch - is that patch
> >> available for looking at somewhere?
> >
> > It was not a hypervisor patch. It was one for the guest. This was the hack:
>
> So then why do you want to patch the upstream kernel? It won't
> make that hack go away, nor will it help any existing kernels.
It will make both distro ditch that patch - and instead they can use this.
[As we can ask them to ditch their crippled patch and they can rest
safely knowing that the upstream kernel has a quirk workaround for what
they had been hitting for ages]
Also with this patch any upstream kernel that runs on Amazon EC2 will not
run in-to the issue that Fedora and Canonical ran with an virgin kernel
when they were deploying it first time. The Amazon EC2 guidelines have it
spelled out somewhere that one can't depend on certain things - even if
they are detected. This was one of them, and MWAIT I believe was the other.
It won't fix existing kernels - that is true but that is not what the
purpose of this patch is.
>
> Jan
next prev parent reply other threads:[~2012-09-07 15:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 11:40 [PATCH/RFC] Fix xsave bug on older Xen hypervisors Stefan Bader
2012-09-07 12:33 ` [Xen-devel] " Jan Beulich
2012-09-07 13:21 ` Stefan Bader
2012-09-07 14:02 ` Jan Beulich
2012-09-07 14:22 ` Justin M. Forbes
2012-09-07 14:54 ` Konrad Rzeszutek Wilk
2012-09-07 14:54 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-09-07 15:43 ` Stefan Bader
2012-09-08 10:18 ` [Xen-devel] " Paolo Bonzini
2012-09-08 10:18 ` Paolo Bonzini
2012-09-10 22:36 ` Matt Wilson
2012-09-10 22:36 ` [Xen-devel] " Matt Wilson
2012-09-07 15:44 ` Jan Beulich
2012-09-07 15:47 ` Stefan Bader
2012-09-07 15:52 ` Jan Beulich
2012-09-07 15:48 ` Konrad Rzeszutek Wilk
2012-09-07 15:48 ` Konrad Rzeszutek Wilk [this message]
2012-09-07 16:13 ` Stefan Bader
2012-09-07 16:13 ` [Xen-devel] " Stefan Bader
2012-09-08 10:28 ` Paolo Bonzini
2012-09-08 10:28 ` Paolo Bonzini
2012-09-07 15:52 ` Jan Beulich
2012-09-07 15:54 ` Ian Campbell
2012-09-07 15:54 ` [Xen-devel] " Ian Campbell
2012-09-08 10:20 ` Paolo Bonzini
2012-09-08 10:20 ` [Xen-devel] " Paolo Bonzini
2012-09-07 15:47 ` Stefan Bader
2012-09-07 16:00 ` [Xen-devel] " Justin M. Forbes
2012-09-11 2:40 ` Matt Wilson
2012-09-11 2:40 ` [Xen-devel] " Matt Wilson
2012-09-11 11:37 ` Konrad Rzeszutek Wilk
2012-09-11 11:37 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-09-11 13:06 ` Josh Boyer
2012-09-11 13:06 ` Josh Boyer
2012-09-07 16:00 ` Justin M. Forbes
2012-09-07 15:44 ` Jan Beulich
2012-09-07 14:22 ` Justin M. Forbes
2012-09-07 14:02 ` Jan Beulich
2012-09-07 13:21 ` Stefan Bader
2012-09-07 12:33 ` Jan Beulich
2012-09-07 13:47 ` Konrad Rzeszutek Wilk
2012-09-07 13:47 ` Konrad Rzeszutek Wilk
2012-09-11 1:17 ` Matt Wilson
2012-09-11 1:17 ` Matt Wilson
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=20120907154827.GA6059@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=jmforbes@linuxtx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msw@amazon.com \
--cc=stefan.bader@canonical.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.