xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Cc: yang.z.zhang@intel.com, kevin.tian@intel.com, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [v5][PATCH 1/2] xen:x86:mm:p2m: introduce set_identity_p2m_entry
Date: Tue, 29 Jul 2014 17:20:22 +0800	[thread overview]
Message-ID: <53D76756.9070304@intel.com> (raw)
In-Reply-To: <53D75F5B.9070002@citrix.com>

On 2014/7/29 16:46, Andrew Cooper wrote:
> On 29/07/2014 09:19, Jan Beulich wrote:
>>>>> On 29.07.14 at 09:35, <tiejun.chen@intel.com> wrote:
>>> On 2014/7/29 15:05, Jan Beulich wrote:
>>>>>>> On 29.07.14 at 08:40, <tiejun.chen@intel.com> wrote:
>>>>> +    struct p2m_domain *p2m = p2m_get_hostp2m(d);
>>>>> +    int ret = -EBUSY;
>>>>> +
>>>>> +    gfn_lock(p2m, gfn, 0);
>>>>> +
>>>>> +    tmp_mfn = p2m->get_entry(p2m, gfn, &p2mt, &a, 0, NULL);
>>>>> +
>>>>> +    if ( mfn_valid(tmp_mfn) )
>>>>> +    {
>>>>> +        gdprintk(XENLOG_ERR,
>>>>> +                 "Overlapping RMRRs at %"PRIx64".\n", (paddr_t)gfn);
>>>> Pointless cast: Just use %lx in the format string. Additionally I don't
>>>> think the message text is correct: You don't really know whether
>>>> what's there is another RMRR (or that the context you're being
>>>> called in refers to an RMRR at all). On the contrary - if it was an
>>>> RMRR (or to be precise, a previously established identity mapping),
>>>> you'd want to report success. And generally we have no stop at
>>>> the end of log messages.
>>> So just print this,
>>>
>>> +        gdprintk(XENLOG_ERR,
>>> +                 "Overlapping at %lx.\n", (paddr_t)gfn);
>> Of course not - such a message is really meaningless.
>>
>> printk(XENLOG_G_WARNING "Cannot identity map %d:%lx, already mapped to %lx\n",
>>         d->domain_id, gfn, mfn_x(mfn));
>>
>> would be a message conveying all information necessary to
>> gain initial understanding of what the issue is.
>
> This would be better as "map d%d:%lx" to indicate that it is a domid
> before the colon.
>

"d" seems hard to understand so just pdate this as "map Dom%d:%lx"

Thanks
Tiejun

  parent reply	other threads:[~2014-07-29  9:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29  6:40 [v5][PATCH 1/2] xen:x86:mm:p2m: introduce set_identity_p2m_entry Tiejun Chen
2014-07-29  6:40 ` [v5][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Tiejun Chen
2014-07-29  7:05 ` [v5][PATCH 1/2] xen:x86:mm:p2m: introduce set_identity_p2m_entry Jan Beulich
2014-07-29  7:35   ` Chen, Tiejun
2014-07-29  8:19     ` Jan Beulich
2014-07-29  8:46       ` Andrew Cooper
2014-07-29  9:05         ` Jan Beulich
2014-07-29  9:20         ` Chen, Tiejun [this message]
2014-07-29  9:43           ` Andrew Cooper
2014-07-29  9:11       ` Chen, Tiejun
2014-07-29  9:53         ` Jan Beulich
2014-07-29 10:18           ` Chen, Tiejun
2014-07-29 10:27             ` Jan Beulich
2014-07-29 11:08               ` Chen, Tiejun
2014-07-29 11:29                 ` 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=53D76756.9070304@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=kevin.tian@intel.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.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).