xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen devel <xen-devel@lists.xen.org>
Subject: Re: Problem about dump-core
Date: Wed, 17 Sep 2014 02:11:12 +0100	[thread overview]
Message-ID: <1410916272.23505.39.camel@citrix.com> (raw)
In-Reply-To: <5418DADE.60006@cn.fujitsu.com>

On Wed, 2014-09-17 at 08:50 +0800, Wen Congyang wrote:

> Yes, we can check it more earlier. If the 4 error bits are set, is it a valid
> mfn?

It doesn't really matter, since valid or not you can't pass such an mfn
to this interface because of the error handling behaviour.

Ian.

  reply	other threads:[~2014-09-17  1:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  2:35 Problem about dump-core Wen Congyang
2014-09-16  7:23 ` Wen Congyang
2014-09-16 16:38   ` Ian Campbell
2014-09-17  0:50     ` Wen Congyang
2014-09-17  1:11       ` Ian Campbell [this message]
2014-09-17  1:14         ` Wen Congyang
2014-09-17  6:56         ` Wen Congyang

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=1410916272.23505.39.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=wency@cn.fujitsu.com \
    --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 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).