From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [RFC PATCH 7/8]: PVH: grant changes
Date: Fri, 17 Aug 2012 17:06:41 -0700 [thread overview]
Message-ID: <20120817170641.4261229b@mantra.us.oracle.com> (raw)
In-Reply-To: <1345197150.30865.147.camel@zakaz.uk.xensource.com>
On Fri, 17 Aug 2012 10:52:30 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> On Thu, 2012-08-16 at 02:06 +0100, Mukesh Rathor wrote:
> > diff --git a/drivers/xen/grant-table.c b/drivers/xen/grant-table.c
> > index 0bfc1ef..2430133 100644
> > --- a/drivers/xen/grant-table.c
> > +++ b/drivers/xen/grant-table.c
> > HYPERVISOR_memory_op(XENMEM_add_to_physmap, &xatp); if (rc != 0) {
> > printk(KERN_WARNING
> > @@ -1053,7 +1058,7 @@ static void gnttab_request_version(void)
> > int rc;
> > struct gnttab_set_version gsv;
> >
> > - if (xen_hvm_domain())
> > + if (xen_hvm_domain() || xen_pvh_domain())
>
> Does something stop pvh using v2?
I had some issue related to grstatus field that was added, so punted it
for now. It's phase II which is a big phase now :) :)...
> >
> > - if (xen_pv_domain())
> > + /* PVH note: xen will free existing kmalloc'd mfn in
> > + * XENMEM_add_to_physmap */
> > + if (xen_pvh_domain() && !gnttab_shared.addr) {
> > + gnttab_shared.addr =
> > + kmalloc(max_nr_gframes * PAGE_SIZE,
> > GFP_KERNEL);
> > + if ( !gnttab_shared.addr ) {
> > + printk(KERN_WARNING "%s", kmsg);
>
> Why this construct instead of just the string literal?
To keep line overflow. I dont' like code spanning 80 columns. If you split,
then you can't grep.
next prev parent reply other threads:[~2012-08-18 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 1:06 [RFC PATCH 7/8]: PVH: grant changes Mukesh Rathor
2012-08-17 9:52 ` Ian Campbell
2012-08-18 0:06 ` Mukesh Rathor [this message]
2012-08-18 8:22 ` Ian Campbell
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=20120817170641.4261229b@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 \
/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).