From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Paul Durrant <paul.durrant@citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] x86/shadow: account for ioreq server pages before complaining about not found mapping
Date: Fri, 29 Apr 2016 18:21:50 +0100 [thread overview]
Message-ID: <5723982E.3010908@citrix.com> (raw)
In-Reply-To: <20160429171022.GB97240@deinos.phlegethon.org>
On 29/04/16 18:10, Tim Deegan wrote:
> At 06:39 -0600 on 29 Apr (1461911995), Jan Beulich wrote:
>>>>> On 29.04.16 at 14:28, <andrew.cooper3@citrix.com> wrote:
>>> It would be nice if we could use gfn_t rather than having more unsigned
>>> longs.
>> I generally agree, but intentionally didn't to match all the other
>> shadow code. I'll make changing this dependent on what Tim
>> thinks.
> Is gfn_t even available here?
Yes. It is available everywhere since c/s 177bd5fb "mem: expose
typesafe mfns/gfns/pfns to common code" (I wonder who acked a patch
like that ;p)
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next parent reply other threads:[~2016-04-29 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160429171022.GB97240@deinos.phlegethon.org>
2016-04-29 17:21 ` Andrew Cooper [this message]
2016-04-29 8:13 [PATCH] x86/shadow: account for ioreq server pages before complaining about not found mapping Jan Beulich
2016-04-29 8:29 ` Paul Durrant
2016-04-29 9:21 ` Jan Beulich
2016-04-29 9:35 ` Paul Durrant
2016-04-29 12:28 ` Andrew Cooper
2016-04-29 12:39 ` Jan Beulich
2016-04-29 13:12 ` Wei Liu
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=5723982E.3010908@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=paul.durrant@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).