From: Christoph Hellwig <hch@infradead.org>
To: Juergen Gross <jgross@suse.com>
Cc: jejb@linux.ibm.com,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Bart Van Assche <bvanassche@acm.org>,
Salvatore Bonaccorso <carnil@debian.org>,
sathya.prakash@broadcom.com,
suganath-prabu.subramani@broadcom.com,
"Martin K. Petersen" <martin.petersen@oracle.com>,
MPT-FusionLinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
adi@kriegisch.at
Subject: Re: Report in downstream Debian: mpt3sas broken with xen dom0 with update to 5.10.149 in 5.10.y.
Date: Mon, 24 Oct 2022 09:58:40 -0700 [thread overview]
Message-ID: <Y1bEQMS5SNTbZO/3@infradead.org> (raw)
In-Reply-To: <30a056c8-071f-4259-3253-75e718af619d@suse.com>
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.
next prev parent reply other threads:[~2022-10-24 20:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 9:22 Report in downstream Debian: mpt3sas broken with xen dom0 with update to 5.10.149 in 5.10.y Salvatore Bonaccorso
2022-10-23 1:27 ` Bart Van Assche
2022-10-24 11:56 ` Sreekanth Reddy
2022-10-24 12:51 ` James Bottomley
2022-10-24 13:20 ` Juergen Gross
2022-10-24 16:58 ` Christoph Hellwig [this message]
2022-10-24 17:28 ` Andrew Cooper
2022-10-24 17:32 ` Christoph Hellwig
[not found] ` <20230314111752.EGroupware.TiNRv1BSroWqKL7zQtfNLJ8@_>
2023-03-14 11:23 ` Juergen Gross
2023-03-14 11:41 ` Andrew Cooper
2023-03-14 12:07 ` Salvatore Bonaccorso
2022-10-24 12:55 ` Juergen Gross
2022-10-24 18:50 ` James Bottomley
2022-10-25 4:32 ` Juergen Gross
2022-10-25 6:38 ` Juergen Gross
2022-10-24 14:58 ` Adi Kriegisch
2022-10-24 17:30 ` Christoph Hellwig
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=Y1bEQMS5SNTbZO/3@infradead.org \
--to=hch@infradead.org \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=adi@kriegisch.at \
--cc=bvanassche@acm.org \
--cc=carnil@debian.org \
--cc=jejb@linux.ibm.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=xen-devel@lists.xenproject.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