From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH V2 6/7]: PVH: balloon and grant changes
Date: Wed, 17 Oct 2012 10:32:06 +0100 [thread overview]
Message-ID: <1350466326.2460.40.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20121016170900.665acf55@mantra.us.oracle.com>
On Wed, 2012-10-17 at 01:09 +0100, Mukesh Rathor wrote:
> > > gsv.version = 1;
> > > else
> > > gsv.version = 2;
> > > @@ -1083,12 +1088,24 @@ static void gnttab_request_version(void)
> > > int gnttab_resume(void)
> > > {
> > > unsigned int max_nr_gframes;
> > > + char *kmsg = "Failed to kmalloc pages for pv in hvm grant
> > > frames\n";
> > > gnttab_request_version();
> > > max_nr_gframes = gnttab_max_grant_frames();
> > > if (max_nr_gframes < nr_grant_frames)
> > > return -ENOSYS;
> > >
> > > + /* PVH note: xen will free existing kmalloc'd mfn in
> > > + * XENMEM_add_to_physmap */
> >
> > It doesn't leak it?
> > We should consider using xenballoon_alloc_pages here.
>
> Well, it's a one time allocation of a dozen (iirc) pages, that are
> returned back to dom heap.
> We could use xenballoon, but for that we
> need to create vma first so we get the contigous VA,
> then map each pte
> since xenballoon_ doesn't return contigous pages, and then populate
> physmap. I'm gonna punt it to phase II. Lets get some working baseline
> in asap.
That's fair enough.
prev parent reply other threads:[~2012-10-17 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 22:01 Mukesh Rathor
2012-10-12 9:06 ` [Xen-devel] " Ian Campbell
2012-10-17 0:09 ` Mukesh Rathor
2012-10-17 9:32 ` 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=1350466326.2460.40.camel@zakaz.uk.xensource.com \
--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
all inboxes | Powered by JetHome®