[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1bEQMS5SNTbZO/3@infradead.org>
Date: Mon, 24 Oct 2022 09:58:40 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Juergen Gross <jgross@...e.com>
Cc: jejb@...ux.ibm.com, Sreekanth Reddy <sreekanth.reddy@...adcom.com>,
Bart Van Assche <bvanassche@....org>,
Salvatore Bonaccorso <carnil@...ian.org>,
sathya.prakash@...adcom.com, suganath-prabu.subramani@...adcom.com,
"Martin K. Petersen" <martin.petersen@...cle.com>,
MPT-FusionLinux.pdl@...adcom.com, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
adi@...egisch.at
Subject: Re: Report in downstream Debian: mpt3sas broken with xen dom0 with
update to 5.10.149 in 5.10.y.
On Mon, Oct 24, 2022 at 03:20:43PM +0200, Juergen Gross wrote:
> Dom0 is (normally) a PV domain, so the physical memory can be still above
> 4 GB even with dom0_mem set to 4GB.
Which means that we need to ensure the DMA ops for Xen-PV (which is
always xen-swiotlb I think?) need to return DMA_BIT_MASK(64) or whatever
is the highest possible address.
Powered by blists - more mailing lists