[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <717bd7ec-229d-02dc-e696-7ede026dbe92@citrix.com>
Date: Wed, 5 Sep 2018 00:36:09 +0100
From: Andrew Cooper <andrew.cooper3@...rix.com>
To: Dongli Zhang <dongli.zhang@...cle.com>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>
CC: John Sobecki <john.sobecki@...cle.com>,
Joe Jin <joe.jin@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
<stable@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen-swiotlb: use actually allocated size on
check physical contiguous
On 05/09/18 00:14, Dongli Zhang wrote:
> Below module would help people reproduce the issue to understand the symptom:
>
> https://github.com/finallyjustice/patchset/blob/master/xen-swiotlb-panic.c
>
> In addition, on the xen hypervisor side, the memory_exchange() in xen hypervisor
> does not check if the the pfn of input mfn belong to the same extent are
> continuous in guest domain. As a result, the wrong page is stolen from guest domain.
>
> Can we assume it is fine to not check if pfn of mfn are continuous in xen
> hypervisor?
The purpose of the memory_exchange hypercall is to exchange any
arbitrary set of guest frames with an equivalently sized set frames with
different properties.
The practical use is for PV guests to be able to create a DMA buffer
which is physically continuous. Xen does not, and indeed should not,
care about the properties of the input frame list.
~Andrew
Powered by blists - more mailing lists