[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Report in downstream Debian: mpt3sas broken with xen dom0 with update to 5.10.149 in 5.10.y.
- To: Juergen Gross <jgross@xxxxxxxx>
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
- Date: Mon, 24 Oct 2022 09:58:40 -0700
- Cc: jejb@xxxxxxxxxxxxx, Sreekanth Reddy <sreekanth.reddy@xxxxxxxxxxxx>, Bart Van Assche <bvanassche@xxxxxxx>, Salvatore Bonaccorso <carnil@xxxxxxxxxx>, sathya.prakash@xxxxxxxxxxxx, suganath-prabu.subramani@xxxxxxxxxxxx, "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, MPT-FusionLinux.pdl@xxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, adi@xxxxxxxxxxxx
- Delivery-date: Mon, 24 Oct 2022 16:59:12 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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.
|
