From: "Jan Beulich" <jbeulich@novell.com>
To: "Sven Köhler" <skoehler@upb.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: [BUG?] Non-privileged (1) attempt to map I/O space 000000f0
Date: Thu, 03 May 2007 08:48:02 +0100 [thread overview]
Message-ID: <4639AFD2.76E4.0078.0@novell.com> (raw)
In-Reply-To: <f1aq4k$u7e$1@sea.gmane.org>
>>> Sven Köhler <skoehler@upb.de> 02.05.07 21:51 >>>
>i'm getting this error after i upgraded to xen 3.0.4-1.
>It seems, that it doesn't harm anything.
>
>Anyway: for any domU i start, i get this in "xm dmesg":
>(XEN) mm.c:566:d1 Non-privileged (1) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d2 Non-privileged (2) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d3 Non-privileged (3) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d4 Non-privileged (4) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d5 Non-privileged (5) attempt to map I/O space
000000f0
This is generally being caused by tools like hwinfo that try to map
BIOS space
(which is meaningless in DomU-s; only Dom0 is allowed to see the real
BIOS
space). Having looked at it quite a while back I thinks there's
nothing
reasonable we can do at the Xen or kernel side, it's the offending tool
that
needs fixing if this message is considered a problem.
Jan
prev parent reply other threads:[~2007-05-03 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 19:51 [BUG?] Non-privileged (1) attempt to map I/O space 000000f0 Sven Köhler
2007-05-03 7:48 ` Jan Beulich [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=4639AFD2.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=skoehler@upb.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 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.