From: Stefan Bader <stefan.bader@canonical.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] xen/x86: Force removal of memory range when not covered by MTRRs
Date: Fri, 22 Feb 2013 14:22:03 +0100 [thread overview]
Message-ID: <512770FB.7060509@canonical.com> (raw)
In-Reply-To: <CAJ75kXZQno5MEeKj39vrNUbwt3fFJ8SeQ4vOXoRJtwR=04WVVA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 722 bytes --]
On 22.02.2013 14:08, William Dauchy wrote:
> On Fri, Feb 15, 2013 at 5:45 PM, Stefan Bader
> <stefan.bader@canonical.com> wrote:
>> Not sure it makes the difference but keep in mind that the report is about a 3.2
>> kernel. They initially claimed that 3.5 works, but then some comments seem to
>> say that was when using dom0_mem= which would in that case work around the bug.
>> Maybe time to go back and ask whether a recent kernel without dom0_mem on the
>> same machine still crashes...
>
> I have the same issue on a dom0 3.4.x (3.4.33 in my case)
>
Hrm, while my reporter claims the affected machine boots with kernel 3.3 and
later. Something is wrong with the picture... somewhere... :/
-Stefan
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-02-22 13:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:11 [PATCH] xen/x86: Force removal of memory range when not covered by MTRRs Stefan Bader
2013-02-15 9:19 ` Jan Beulich
2013-02-15 10:34 ` Stefan Bader
2013-02-15 11:13 ` Jan Beulich
2013-02-15 11:31 ` Stefan Bader
2013-02-15 13:47 ` Konrad Rzeszutek Wilk
2013-02-15 14:00 ` Keir Fraser
2013-02-15 14:52 ` Jan Beulich
2013-02-15 16:40 ` Konrad Rzeszutek Wilk
2013-02-15 16:45 ` Stefan Bader
2013-02-22 13:08 ` William Dauchy
2013-02-22 13:22 ` Stefan Bader [this message]
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=512770FB.7060509@canonical.com \
--to=stefan.bader@canonical.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=wdauchy@gmail.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.