All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Patrick Colp <pjcolp@cs.ubc.ca>
Cc: xen-devel@lists.xensource.com
Subject: Re: xenpaging crashes xen in is_iomem_page()
Date: Fri, 6 Aug 2010 13:16:20 +0200	[thread overview]
Message-ID: <20100806111620.GA457@aepfle.de> (raw)
In-Reply-To: <AANLkTi=Zqwg1F6k3Nq15NnQVSuJRE8xuFsqOeg54ukuP@mail.gmail.com>

On Tue, Jul 27, Patrick Colp wrote:

> I pulled the latest version of Xen (revision 21859) and ran it on my
> EPT box and then ran xenpaging and it's working fine for me.

Patrick,

after playing a bit more with xenpaging, its not working for me.

Whats your environment?

I have a plain SLES11 SP1 x86_64 installation on a Xeon X5550 box.
The client is also a plain SLES11 SP1 x86_64.
Once I boot the client and start xenpaging with 256mb, the client gets
lots of SIGBUS or SIGSEGV.
Xen prints 'Iomem mapping not permitted ffffffffff (domain 1)' in
grant_table.c:__gnttab_map_grant_ref() 


Olaf

  parent reply	other threads:[~2010-08-06 11:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 11:58 xenpaging crashes xen in is_iomem_page() Olaf Hering
2010-07-26 13:15 ` Patrick Colp
2010-07-26 14:08   ` Olaf Hering
2010-07-26 14:39     ` Patrick Colp
2010-07-26 14:58       ` Tim Deegan
2010-07-26 15:23         ` Patrick Colp
2010-07-27 15:20   ` Olaf Hering
2010-07-27 15:46     ` Patrick Colp
2010-07-27 18:25       ` Olaf Hering
2010-07-27 18:39         ` Patrick Colp
2010-07-28 15:26           ` Olaf Hering
2010-07-28 16:22             ` Patrick Colp
2010-08-06 11:16       ` Olaf Hering [this message]
2010-08-09 13:30         ` Patrick Colp
2010-08-09 17:39           ` Olaf Hering
2010-08-09 18:23             ` Patrick Colp
2010-08-10 14:19               ` Olaf Hering
2010-08-10 15:02                 ` Patrick Colp
2010-08-10 15:06                   ` Olaf Hering

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=20100806111620.GA457@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=pjcolp@cs.ubc.ca \
    --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.