From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien.grall@arm.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii_anisov@epam.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [TESTDAY] Test report
Date: Thu, 25 May 2017 11:41:19 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1705251135520.18759@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <235bc693-cd31-006f-9672-0104ce2e72ae@arm.com>
On Thu, 25 May 2017, Julien Grall wrote:
> Hi Andrii,
>
> On 23/05/17 18:03, Andrii Anisov wrote:
> > * Hardware:
> > Salvator-X board with Renesas R-Car H3 SoC (ARM64)
> >
> > * Software:
> > XEN 4.9-rc6
> > System based on Renesas Yocto 2.19.0 BSP [1]
> > Linux kernel 4.9
> >
> > * Guest operating systems:
> > The same system as dom0.
> >
> > * Functionality tested:
> > xl create/restart/shutdown
> > Guest domain reboot from its console
> > PV NET (nfsroot in domU) , PV Block (copy from xvda to nfsroot in DomU)
> >
> > * Comments:
> >
> > On DomU startup messages like following appeared:
> >
> > root@salvator-x-domx:~# (XEN) printk: 9 messages suppressed.
> > (XEN) d1v0: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> > (XEN) d1v1: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> > (XEN) d1v2: vGICD: unhandled word write 0xffffffff to ICACTIVER0
> > (XEN) d1v3: vGICD: unhandled word write 0xffffffff to ICACTIVER0
>
> The vGIC emulation does not emulate I*ACTIVER* registers so far. But Linux
> only accesses them at boot to ensure the firmware didn't leave interrupt in
> active state. They are harmless for now.
>
> > [ 65.333062] xen-blkback: backend/vbd/1/51713: using 4 queues,
> > protocol 1 (arm-abi) persistent grants
> > [ 65.357846] xen-blkback: backend/vbd/1/51714: using 4 queues,
> > protocol 1 (arm-abi) persistent grants
> > [ 65.514054] vif vif-1-0 vif1.0: Guest Rx ready
> > [ 65.518485] IPv6: ADDRCONF(NETDEV_CHANGE): vif1.0: link becomes
> > ready
> > [ 65.525021] xenbr0: port 2(vif1.0) entered blocking state
> > [ 65.530359] xenbr0: port 2(vif1.0) entered forwarding state
> > [ 65.815976] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x0000000000063772 -> mfn=0x000000000072abb0: pfn=0x0000000000063772
> > -> mfn=0x0000000000727aad already exists
> > [ 65.834442] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x000000000006374e -> mfn=0x000000000072abb0: pfn=0x000000000006374e
> > -> mfn=0x0000000000727aad already exists
> > [ 66.025979] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x000000000006379c -> mfn=0x000000000072abb3: pfn=0x000000000006379c
> > -> mfn=0x000000000072abb1 already exists
> > [ 66.273534] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x0000000000063731 -> mfn=0x0000000000727c3d: pfn=0x0000000000063731
> > -> mfn=0x0000000000727c3e already exists
> > [ 66.328245] xen_add_phys_to_mach_entry: cannot add
> > pfn=0x00000000000637ee -> mfn=0x0000000000727c3f: pfn=0x00000000000637ee
> > -> mfn=0x0000000000727c3d already exists
>
> I was expecting Stefano to answer here as he knows better than me this part of
> the code.
>
> Linux is storing the conversion between pfn (guest frame number) to the mfn
> (machine frame number) in an RB-tree. This will be used by the swiotlb code to
> know if a buffer is contiguous in the physical RAM.
>
> In your case, the log says that there was already a mapping pfn <-> mfn in the
> tree. It looks to me the previous mapping has not been removed correctly.
>
> Are you able to reproduce this reliably? If so, can you try to figure out who
> added the first mapping pfn <-> mfn?
Sorry, I skimmed over the email and missed those warnings.
Julien, you are correct. The mappings are added by
set_foreign_p2m_mapping, which is called on gnttab_map_refs, and should
be removed by clear_foreign_p2m_mapping, called by gnttab_unmap_refs.
Maybe the mapping function is called twice or the unmapping function is
not called when it should?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-25 18:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:03 [TESTDAY] Test report Andrii Anisov
2017-05-23 20:14 ` Stefano Stabellini
2017-05-25 10:17 ` Julien Grall
2017-05-25 18:41 ` Stefano Stabellini [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-13 20:34 Edgar E. Iglesias
2016-05-14 18:15 ` Julien Grall
2016-05-14 19:04 ` Edgar E. Iglesias
2016-05-16 9:58 ` Wei Liu
2016-05-16 13:20 ` Julien Grall
2016-05-16 13:41 ` Edgar E. Iglesias
2016-05-16 13:43 ` Julien Grall
2016-05-13 15:14 Tamas K Lengyel
2015-10-01 16:59 Tamas K Lengyel
2015-10-01 17:04 ` Wei Liu
2014-10-30 10:54 Jan Vejvalka
2014-10-30 14:39 ` Ian Campbell
2014-10-31 6:35 ` Jan Vejvalka
2014-10-30 14:58 ` Roger Pau Monné
2014-01-20 22:49 Don Slutz
2014-01-20 23:35 ` Konrad Rzeszutek Wilk
2014-01-23 10:51 ` Ian Campbell
2014-01-23 22:03 ` Don Slutz
2014-01-24 14:58 ` Konrad Rzeszutek Wilk
2014-01-24 16:43 ` Don Slutz
2014-01-24 19:06 ` Don Slutz
2014-01-24 19:20 ` Konrad Rzeszutek Wilk
2014-01-27 1:15 ` herbert cland
2012-09-19 7:04 Dariusz Krempa
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=alpine.DEB.2.10.1705251135520.18759@sstabellini-ThinkPad-X260 \
--to=sstabellini@kernel.org \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.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).