From: Keir Fraser <keir.fraser@eu.citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: DOMID_XEN and iomem_access_permitted
Date: Thu, 13 May 2010 10:09:56 +0100 [thread overview]
Message-ID: <C8118074.1422F%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <AANLkTinh4T3vDyES59tf_S6xxh8yr2irLArzoUNvO374@mail.gmail.com>
On 12/05/2010 21:45, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
> Actually, setting up an empty rangeset for the "xen" domain might be
> the best solution... it works no matter what the answers above are,
> and has fewer special cases in the code. Looks like it would mainly
> involve actually initializing the rangeset code even for dummy domains
> in domian_create().
Fixed as xen-unstable:21373, and I will also backport for 4.0.1 and 3.4.3.
-- Keir
prev parent reply other threads:[~2010-05-13 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 20:45 DOMID_XEN and iomem_access_permitted George Dunlap
2010-05-12 20:48 ` Keir Fraser
2010-05-12 20:55 ` George Dunlap
2010-05-13 9:09 ` Keir Fraser [this message]
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=C8118074.1422F%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).