xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Carsten Schiers <carsten@schiers.de>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: AW: Re: Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21  pvops Kernel?
Date: Fri, 10 Sep 2010 09:48:33 +0100	[thread overview]
Message-ID: <4C8A0D010200007800015611@vpn.id2.novell.com> (raw)
In-Reply-To: <H000006700083044.1284056830.uhura.space.zz@MHS>

>>> On 09.09.10 at 20:27, "Carsten Schiers" <carsten@schiers.de> wrote:
> and provided the output, just in case it is what you needed. I will for 
> sure need some time to understand that.
> Is the hypothesis that a) the BIOS is wrong, and b) Xen is checking more 
> extreme than bare metal, so we need to
> make the Xen Code a bit more relaxed (error message instead of crash)?

I think the underlying problem was pointed out before: The page table
accessor functions can't currently propagate errors, and hence
ioremap() can't be forced to fail if Xen refused a mapping. And then, as
I wrote in an earlier reply, the check for not trying to map RAM from
ioremap() is pretty pointless (and hence no help) currently for the Xen
case.

Jan

  parent reply	other threads:[~2010-09-10  8:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 12:15 Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Carsten Schiers
2010-09-08 12:51 ` Jan Beulich
2010-09-08 20:15   ` AW: " Carsten Schiers
2010-09-09  9:57     ` Jan Beulich
2010-09-09 18:27       ` Carsten Schiers
2010-09-09 18:40         ` Carsten Schiers
2010-09-09 19:04           ` Carsten Schiers
2010-09-10  8:22             ` Jan Beulich
2010-09-10  8:45           ` Jan Beulich
2010-09-14  9:10             ` Carsten Schiers
2010-09-14  9:33               ` Jan Beulich
2010-09-14 21:19                 ` AW: Re: ACPI problem, was " Carsten Schiers
2010-09-14 22:05                   ` Jeremy Fitzhardinge
2010-09-15  1:20                     ` Yu, Ke
2010-09-15  2:02                       ` Wang, Winston L
2010-09-15  5:37                         ` Jiang, Yunhong
2010-09-15  7:22                           ` AW: " Carsten Schiers
2010-09-15  7:38                             ` Jiang, Yunhong
2010-09-15  8:15                             ` AW: " Jan Beulich
2010-09-15  8:28                               ` Carsten Schiers
2010-09-15  8:36                               ` Jiang, Yunhong
2010-09-15  8:50                               ` Jiang, Yunhong
2010-10-19  9:59                                 ` 2.6.34.7 with SUSE patches: Invalid Kernel Carsten Schiers
2010-10-20 16:54                                   ` Jeremy Fitzhardinge
2010-09-15 17:01                           ` AW: Re: ACPI problem, was Xen BUG in mm / Xen 4.0.1 with 2.6.32.18/21 pvops Kernel? Jeremy Fitzhardinge
2010-09-10  8:48         ` Jan Beulich [this message]
2010-09-08 20:16   ` AW: " Carsten Schiers

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=4C8A0D010200007800015611@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=carsten@schiers.de \
    --cc=xen-devel@lists.xensource.com \
    /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).