From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-devel] [PATCH V2 3/7]: PVH: mmu related changes.
Date: Tue, 16 Oct 2012 20:43:08 +0100 [thread overview]
Message-ID: <1350416588.28188.0.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <20121016104657.4b2478a8@mantra.us.oracle.com>
On Tue, 2012-10-16 at 10:46 -0700, Mukesh Rathor wrote:
> On Tue, 16 Oct 2012 17:27:01 +0100
> Ian Campbell <Ian.Campbell@citrix.com> wrote:
>
> > On Fri, 2012-10-12 at 09:57 +0100, Ian Campbell wrote:
> > > > +int xen_unmap_domain_mfn_range(struct vm_area_struct *vma)
> > > > +{
> > > > + int numpgs = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
> > > > + struct page **pages = vma ? vma->vm_private_data : NULL;
> > >
> > > I thought we agreed to keep uses of vm_private_data in the privcmd
> > > driver?
> > >
> > > I think you should just add pages and nr as direct parameters to
> > > this function, which is symmetric with the map call.
> >
> > I had to look at this while rebasing my arm patches, turned out to be
> > fairly simple. Feel free to either fold in or badger me for a proper
> > commit message.
>
>
> I made similar change in my tree, except I am not passing vma as its
> not needed. I guess you just wanna be consistend with remap, or future
> use?
Consistency mostly.
prev parent reply other threads:[~2012-10-16 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 21:58 Mukesh Rathor
2012-10-12 8:57 ` [Xen-devel] " Ian Campbell
2012-10-12 22:36 ` Mukesh Rathor
2012-10-16 16:27 ` Ian Campbell
2012-10-16 17:46 ` Mukesh Rathor
2012-10-16 19:43 ` Ian Campbell [this message]
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=1350416588.28188.0.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.rathor@oracle.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
Powered by JetHome