From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: vm_event regression in 4.7
Date: Wed, 3 Feb 2016 01:00:10 +0000 [thread overview]
Message-ID: <56B1511A.6010505@citrix.com> (raw)
In-Reply-To: <CABfawhnONZU45qt7AbHs0NnfE9xDT-L95uVaBv+QLm2TKW2EGw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1197 bytes --]
On 03/02/2016 00:51, Tamas K Lengyel wrote:
> Hello all,
> with the latest master branch of Xen there is a regression enabling
> vm_event on a domain. If an event listener was previously active on
> the domain it is now not possible to reenable events as the domctl
> returns -EINVAL. The problem seems to stem from activating the magic
> page for vm_event using prepare_ring_for_helper as it returns NULL.
> Further looking into where things go wrong within that function it
> seems the page type returned by __get_gfn_type_access is
> p2m_ram_logdirty with an invalid mfn (0xffffffffffffffff) and then it
> hits "Error path: not a suitable GFN at all".
>
> Can anyone point me to which change or what may be causing this?
Did the previous event listener replace the page it stole from guest
physmap for ring purposes when it exited?
That error specifically means that the gfn chosen for the ring was not
present when prepare_ring_for_helper() was called.
A first gut feeling would point to the changed in HVM domain
construction stemming from the DMLite work, but if event listening works
for the first time and then fails, the magic page was suitably present
the first time around.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2071 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-03 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 0:51 vm_event regression in 4.7 Tamas K Lengyel
2016-02-03 1:00 ` Andrew Cooper [this message]
2016-02-03 1:32 ` Tamas K Lengyel
2016-02-03 10:35 ` Andrew Cooper
2016-02-05 20:34 ` Tamas K Lengyel
2016-02-05 21:08 ` Tamas K Lengyel
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=56B1511A.6010505@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=tamas.k.lengyel@gmail.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).