From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [RFC PATCH 14/16]: PVH xen: add xenmem_add_foreign_to_pmap()
Date: Wed, 13 Feb 2013 18:34:25 -0800 [thread overview]
Message-ID: <20130213183425.0d17c236@mantra.us.oracle.com> (raw)
In-Reply-To: <20130211181824.169b9d05@mantra.us.oracle.com>
On Mon, 11 Feb 2013 18:18:24 -0800
Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> On Thu, 24 Jan 2013 17:31:18 +0000
> Tim Deegan <tim@xen.org> wrote:
>
> > At 18:11 -0800 on 11 Jan (1357927863), Mukesh Rathor wrote:
> >
> > > + /* qemu, running on PVH dom0, mapping hvm domain's io pages
> > > during domain
> > > + * creation, doesn't have mfns in the HAP table */
> > > + if ( !mfn_valid(mfn) && p2m_is_mmio(p2mt) ) {
> >
> > This test should be for == p2m_mmio_direct; we don't want to try
> > mapping p2m_mmio_dm areas.
>
> Yup. Done.
No, qemu is changing the mem type for these pages, so I need to dig
into understanding what it's trying to do there. But the above, I don't
think is correct. Xen returns p2m type of dm, but I don't think I'm
looking at right mfn's here for this qemu special case. Basically, it's
during hvm guest creation on PVH dom0 that qemu accesses some addresses
that are not mapped.
Anyways, I hope to figure whats going on in qemu soon.
thanks,
Mukesh
next prev parent reply other threads:[~2013-02-14 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 2:11 [RFC PATCH 14/16]: PVH xen: add xenmem_add_foreign_to_pmap() Mukesh Rathor
2013-01-24 17:31 ` Tim Deegan
2013-02-12 2:18 ` Mukesh Rathor
2013-02-14 2:34 ` Mukesh Rathor [this message]
2013-02-14 10:22 ` Tim Deegan
2013-02-14 10:39 ` Tim Deegan
2013-02-16 0:17 ` Mukesh Rathor
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=20130213183425.0d17c236@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=tim@xen.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 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).