All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: IOCTL_PRIVCMD_MMAPBATCH on Xen 4.13.0
Date: Sun, 17 May 2020 19:32:59 +0200	[thread overview]
Message-ID: <20200517173259.GA7285@antioche.eu.org> (raw)
In-Reply-To: <d22b6b7c-9d1c-4cfb-427a-ca6f440a9b08@citrix.com>

I've been looking a bit deeper in the Xen kernel.
The mapping is failed in ./arch/x86/mm/p2m.c:p2m_get_page_from_gfn(),
        /* Error path: not a suitable GFN at all */
	if ( !p2m_is_ram(*t) && !p2m_is_paging(*t) && !p2m_is_pod(*t) ) {
	    gdprintk(XENLOG_ERR, "p2m_get_page_from_gfn2: %d is_ram %ld is_paging %ld is_pod %ld\n", *t, p2m_is_ram(*t), p2m_is_paging(*t), p2m_is_pod(*t) );
	    return NULL;
	}

*t is 4, which translates to p2m_mmio_dm

it looks like p2m_get_page_from_gfn() is not ready to handle this case
for dom0.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--


  parent reply	other threads:[~2020-05-17 17:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 20:29 IOCTL_PRIVCMD_MMAPBATCH on Xen 4.13.0 Manuel Bouyer
2020-05-15 21:00 ` Andrew Cooper
2020-05-15 21:06   ` Manuel Bouyer
2020-05-15 21:38     ` Andrew Cooper
2020-05-15 21:53       ` Manuel Bouyer
2020-05-16 16:18         ` Andrew Cooper
2020-05-17  9:30           ` Manuel Bouyer
2020-05-17 17:32           ` Manuel Bouyer [this message]
2020-05-17 17:56             ` Manuel Bouyer
2020-05-18  7:36               ` Paul Durrant
2020-05-18 17:31                 ` Manuel Bouyer
2020-05-19  7:34                   ` Jan Beulich
2020-05-19  8:46                     ` Manuel Bouyer
2020-05-19  8:51                       ` Jan Beulich
2020-05-19  9:54               ` Roger Pau Monné
2020-05-19 10:28                 ` Manuel Bouyer

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=20200517173259.GA7285@antioche.eu.org \
    --to=bouyer@antioche.eu.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.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.