All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, armbru@redhat.com,
	JBeulich@novell.com, Ian.Campbell@eu.citrix.com,
	Olivier NOEL <ONOEL@tetra-info.com>,
	keir.fraser@eu.citrix.com
Subject: Re: Re: mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a + (XEN) mm.c:845:d20 Error getting mfn jd (pfn	84fd) from L1 entry 800000000246d467 for l1e_owner=20,	pg_owner=32753
Date: Tue, 01 Dec 2009 14:44:49 -0800	[thread overview]
Message-ID: <4B159C61.4080403@goop.org> (raw)
In-Reply-To: <20091201215745.GA17250@phenom.dumpdata.com>

On 12/01/09 13:57, Konrad Rzeszutek Wilk wrote:
>> 1a) add a flag to avoid setting VM_IO?  (uncompiled, untested, uneverything)
>>     
> That did it. Tested with Dom0 and DomU succesfully.
>
> Signed off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>   

Oh, good.  Could you look at splitting it into a pair of patches
(separate fbdev + xen), and see if you can raise a maintainer ACK (Jaya
Kumar <jayakumar.lkml@gmail.com>, by the look of it)?  Also, are there
any other places which should be testing FBDEV_VIRTFB (does
fbmem.c:fb_mmap() come into play)?

Thanks,
    J

  reply	other threads:[~2009-12-01 22:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-03  9:44 kernel BUG at arch/x86/xen/multicalls.c:103! Olivier NOEL
2009-08-04 23:55 ` Jeremy Fitzhardinge
2009-08-05  7:10   ` Olivier NOEL
2009-08-06  6:50     ` Olivier NOEL
2009-08-06 19:35       ` Jeremy Fitzhardinge
2009-11-09 23:50         ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a Konrad Rzeszutek Wilk
2009-11-10  0:20           ` Jeremy Fitzhardinge
2009-12-01  3:11           ` mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a + (XEN) mm.c:845:d20 Error getting mfn jd (pfn 84fd) from L1 entry 800000000246d467 for l1e_owner=20, pg_owner=32753 Konrad Rzeszutek Wilk
2009-12-01  6:40             ` Jeremy Fitzhardinge
2009-12-01 21:57               ` Konrad Rzeszutek Wilk
2009-12-01 22:44                 ` Jeremy Fitzhardinge [this message]
2009-12-01 23:05                   ` Konrad Rzeszutek Wilk
2009-12-01  9:26             ` Markus Armbruster
2009-12-01 16:14               ` Konrad Rzeszutek Wilk

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=4B159C61.4080403@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=ONOEL@tetra-info.com \
    --cc=armbru@redhat.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --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.