All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>, Tim Deegan <tim@xen.org>,
	IanJackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org,
	Malcolm Crossley <malcolm.crossley@citrix.com>
Subject: Re: [PATCH] xen/domctl: lower loglevel of XEN_DOMCTL_memory_mapping
Date: Thu, 10 Sep 2015 16:55:24 +0800	[thread overview]
Message-ID: <55F1457C.5000708@intel.com> (raw)
In-Reply-To: <55F157D602000078000A18C4@prv-mh.provo.novell.com>

> Sort of (the patch has the intended effect, but for its size very
> many rough edges).
>

I guess we need to amend the original parameter, once_mapping_mfns, like 
this,

/* xen_once_mapping_mfns: memory mapping mfn bumbers once. */
unsigned int xen_once_mapping_mfns;
size_param("once_mapping_mfns", xen_once_mapping_mfns);

static void xen_once_mapping_mfns_setup(void)
{
     if ( once_mapping_mfns < 64 )
         xen_once_mapping_mfns = 64;
     else if ( once_mapping_mfns > 1024 )
         xen_once_mapping_mfns = 1024;
     else
         xen_once_mapping_mfns = once_mapping_mfns;
}

Or what is your expected rule?

Thanks
Tiejun

  reply	other threads:[~2015-09-10  8:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09  6:50 [PATCH] xen/domctl: lower loglevel of XEN_DOMCTL_memory_mapping Tiejun Chen
2015-09-09 14:20 ` Konrad Rzeszutek Wilk
2015-09-09 14:33   ` Jan Beulich
2015-09-09 14:50     ` Konrad Rzeszutek Wilk
2015-09-09 14:55       ` Jan Beulich
2015-09-09 15:05         ` Konrad Rzeszutek Wilk
2015-09-09 15:19       ` Malcolm Crossley
2015-09-09 15:44         ` Jan Beulich
2015-09-10  5:28           ` Chen, Tiejun
2015-09-10  8:13             ` Jan Beulich
2015-09-10  8:55               ` Chen, Tiejun [this message]
2015-09-10  8:59                 ` Jan Beulich
2015-09-10 17:55                   ` Konrad Rzeszutek Wilk
2015-09-11  0:44                     ` Chen, Tiejun
2015-09-11  0:59                       ` Konrad Rzeszutek Wilk
2015-09-11  9:17                         ` Jan Beulich
2015-09-11 10:28                           ` Malcolm Crossley
2015-09-11 11:11                             ` Jan Beulich
2015-09-11 12:05                               ` Malcolm Crossley
2015-09-11 14:11                                 ` Jan Beulich

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=55F1457C.5000708@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=JBeulich@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=malcolm.crossley@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.