From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: david.vrabel@citrix.com, Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: identify a Xen PV domU to fix devmem_is_allowed
Date: Mon, 6 Jun 2016 23:17:17 +0200 [thread overview]
Message-ID: <20160606211717.GA934@aepfle.de> (raw)
In-Reply-To: <56F190CF.8010305@oracle.com>
On Tue, Mar 22, Boris Ostrovsky wrote:
> Can you apply PAT changes from
> http://lists.xenproject.org/archives/html/xen-devel/2016-03/msg02127.html
> and see if it helps?
>
> It should at least get rid of the splat (patch 3 is the one addresses
> no-MTRR problem that I mentioned above). We should still fix
> devmem_is_allowed() though.
Boris, using 02f037d^..b6350c2 fixes biosdevname in dom0 and reading
/dev/mem in a PV domU. Thanks.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-06 21:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 10:28 identify a Xen PV domU to fix devmem_is_allowed Olaf Hering
2016-02-29 15:10 ` Konrad Rzeszutek Wilk
2016-02-29 15:29 ` Olaf Hering
2016-02-29 18:32 ` Boris Ostrovsky
2016-03-01 15:14 ` Olaf Hering
2016-03-01 10:38 ` Jan Beulich
2016-03-01 14:34 ` Konrad Rzeszutek Wilk
2016-03-01 14:45 ` Boris Ostrovsky
2016-03-15 16:57 ` Olaf Hering
2016-03-15 18:56 ` Boris Ostrovsky
2016-03-21 21:29 ` Boris Ostrovsky
2016-03-22 18:37 ` Boris Ostrovsky
2016-03-23 8:28 ` Olaf Hering
2016-06-06 21:17 ` Olaf Hering [this message]
2016-03-01 16:23 ` Olaf Hering
2016-03-01 15:29 ` David Vrabel
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=20160606211717.GA934@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.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 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.