From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH v1 2/8]: PVH mmu changes
Date: Tue, 2 Oct 2012 15:22:31 -0700 [thread overview]
Message-ID: <20121002152231.0c5d7b26@mantra.us.oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1210021219100.29232@kaball.uk.xensource.com>
On Tue, 2 Oct 2012 12:23:58 +0100
Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> On Mon, 1 Oct 2012, Mukesh Rathor wrote:
> > On Mon, 1 Oct 2012 14:32:44 -0700
> > Mukesh Rathor <mukesh.rathor@oracle.com> wrote:
> >
> > >
> > > So, the mapcount must be not be getting set in "normal" case
> > > properly it appears. Marking it special causes it so skip few
> > > things. Debugging...
> >
> > Shall I just leave it special for now, and come back and revisit
> > this later?
>
> special is going to create troubles if somebody starts using these
> pages in unexpected ways (for example dma from hardware ot gupf).
>
> Also I fail to see how this case is any different from mapping pages
> using gntdev (see gntdev_mmap) that works fine without special.
>
> Maybe we are not setting some vm_flags that we are supposed to set
> (VM_RESERVED | VM_IO | VM_DONTCOPY)?
> I see that we are setting them in privcmd_mmap but not in
> privcmd_ioctl_mmap_batch...
No, that is getting set. privcmd_mmap is hook for mmap(), so it gets
called for both. If its not marked special, vm_normal_page() will not
check for the VM_PFNMAP flag, which is what we want.
It works for PV dom0 because remap_area_mfn_pte_fn() has also marked it
special:
static int remap_area_mfn_pte_fn(pte_t *ptep, pgtable_t token,
unsigned long addr, void *data)
{
struct remap_data *rmd = data;
pte_t pte = pte_mkspecial(pfn_pte(rmd->mfn++, rmd->prot));
thanks,
Mukesh
next prev parent reply other threads:[~2012-10-02 22:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:15 [PATCH v1 2/8]: PVH mmu changes Mukesh Rathor
2012-09-24 11:55 ` Stefano Stabellini
2012-09-24 12:16 ` Ian Campbell
2012-09-24 12:24 ` Stefano Stabellini
2012-09-26 0:27 ` Mukesh Rathor
2012-09-26 11:10 ` George Dunlap
2012-09-26 11:16 ` Stefano Stabellini
2012-09-24 13:50 ` Konrad Rzeszutek Wilk
2012-09-26 0:09 ` Mukesh Rathor
2012-09-26 11:15 ` Stefano Stabellini
2012-10-01 21:32 ` Mukesh Rathor
2012-10-01 21:44 ` Mukesh Rathor
2012-10-02 11:23 ` Stefano Stabellini
2012-10-02 22:22 ` Mukesh Rathor [this message]
2012-10-02 10:46 ` Stefano Stabellini
2012-10-03 18:27 ` Mukesh Rathor
2012-10-04 8:18 ` Ian Campbell
2012-09-24 14:04 ` Stefano Stabellini
2012-09-24 14:13 ` Ian Campbell
2012-09-26 0:33 ` Mukesh Rathor
2012-09-26 11:25 ` Stefano Stabellini
2012-09-26 13:54 ` Konrad Rzeszutek Wilk
2012-10-02 10:49 ` Stefano Stabellini
2012-10-03 15:42 ` Ian Campbell
2012-10-03 22:29 ` Mukesh Rathor
2012-10-04 8:27 ` Ian Campbell
2012-10-04 18:27 ` Mukesh Rathor
2012-10-04 18:42 ` Konrad Rzeszutek Wilk
2012-10-05 9:25 ` Ian Campbell
2012-10-06 2:00 ` Mukesh Rathor
2012-10-08 9:31 ` Ian Campbell
2012-10-04 8:31 ` Ian Campbell
2012-10-05 1:17 ` Mukesh Rathor
2012-10-05 9:26 ` Ian Campbell
2012-10-04 13:54 ` Ian Campbell
2012-10-05 1:51 ` 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=20121002152231.0c5d7b26@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.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 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).